Felix Kölzow
2020-Oct-07 19:12 UTC
[Gluster-users] Explanation of gluster vol geo-repliation options
Dear Community, actually, I am looking for a more detailed explaination of all geo-replication options which can be obtained by the command: gluster volume geo-replication master-vol slave-node::slave-volume config I only found https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/ but i am wondering if there is a more detailed explanation of all the other options listed below. Thanks in advance. Felix access_mount:false allow_network: change_detector:changelog change_interval:5 changelog_archive_format:%Y%m changelog_batch_size:727040 changelog_log_file:/var/log/glusterfs/geo-replication/ changelog_log_level:INFO checkpoint:0 cli_log_file:/var/log/glusterfs/geo-replication/cli.log cli_log_level:INFO connection_timeout:60 georep_session_working_dir:/var/lib/glusterd/geo-replication gfid_conflict_resolution:true gluster_cli_options: gluster_command:gluster gluster_command_dir:/usr/sbin gluster_log_file:/var/log/glusterfs/geo-replication/ gluster_log_level:INFO gluster_logdir:/var/log/glusterfs gluster_params:aux-gfid-mount acl gluster_rundir:/var/run/gluster glusterd_workdir:/var/lib/glusterd gsyncd_miscdir:/var/lib/misc/gluster/gsyncd ignore_deletes:false isolated_slaves: log_file:/var/log/glusterfs/geo-replication/ log_level:INFO log_rsync_performance:true master_disperse_count:1 master_distribution_count:2 master_replica_count:1 max_rsync_retries:10 meta_volume_mnt:/var/run/gluster/shared_storage pid_file: remote_gsyncd: replica_failover_interval:1 rsync_command:rsync rsync_opt_existing:true rsync_opt_ignore_missing_args:true rsync_options:-h rsync_ssh_options: slave_access_mount:false slave_gluster_command_dir:/usr/sbin slave_gluster_log_file:/var/log/glusterfs/geo-replication-slaves/ slave_gluster_log_file_mbr:/var/log/glusterfs/geo-replication-slaves slave_gluster_log_level:INFO slave_gluster_params:aux-gfid-mount acl slave_log_file:/var/log/glusterfs/geo-replication-slaves/ slave_log_level:INFO slave_timeout:120 special_sync_mode: ssh_command:ssh ssh_options:-oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem ssh_options_tar:-oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem ssh_port:22 state_file:/var/lib/glusterd/geo-replication/ state_socket_unencoded: stime_xattr_prefix: sync_acls:true sync_jobs:3 sync_method:rsync sync_xattrs:true tar_command:tar use_meta_volume:true use_rsync_xattrs:false working_dir:/var/lib/misc/gluster/gsyncd/.....
Aravinda VK
2020-Oct-08 06:37 UTC
[Gluster-users] Explanation of gluster vol geo-repliation options
Hi Felix, I am adding the details inline. Will open an issue to update the doc. Thanks for reporting. Let me know if any of these needs more clarity.> On 08-Oct-2020, at 12:42 AM, Felix K?lzow <felix.koelzow at gmx.de> wrote: > > Dear Community, > > > actually, I am looking for a more detailed explaination of all > geo-replication options which can be obtained by the command: > > > gluster volume geo-replication master-vol slave-node::slave-volume config > > > I only found > > https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/ > > but i am wondering if there is a more detailed explanation of all the > other options listed below. > > > Thanks in advance. > > Felix > > access_mount:falseInternal Gluster mounts created by Geo-rep are not accessible from outside. With this option, these mounts can be accessed from outside. Useful for debugging purposes.> allow_network: > change_detector:changelogUse changelogs to detect the changes happened in the Primary Volume. Other available option is xsync which is File system crawl and known limitation to detect deletes.> change_interval:5Changelogs rollover interval> changelog_archive_format:%Y%mProcessed changelogs will be stored in working directory partitioned by the specified format.> changelog_batch_size:727040Bytes to limit the changelogs in Batches. Mostly useful if backlog to sync is more.> changelog_log_file:/var/log/glusterfs/geo-replication/Changelogs processing log files directory> changelog_log_level:INFOChangelogs processing log level> checkpoint:0Time will be set here when checkpoint command is run.> cli_log_file:/var/log/glusterfs/geo-replication/cli.logCLI Log file path> cli_log_level:INFOCLI log level> connection_timeout:60> georep_session_working_dir:/var/lib/glusterd/geo-replicationGeo-rep Working dir to store config, status etc> gfid_conflict_resolution:trueThis enables automatic resolution to GFID conflicts in Secondary Volume.> gluster_cli_options:Geo-rep runs Gluster CLI when needed, any extra options can be provided using this.> gluster_command:glusterIf command name is different.> gluster_command_dir:/usr/sbinIf gluster command is not in PATH(gluster_command_dir=/usr/local/sbin)> gluster_log_file:/var/log/glusterfs/geo-replication/Gluster mount(Mounted by Geo-rep process) log directory> gluster_log_level:INFOGluster mount(Mounted by Geo-rep process) log level> gluster_logdir:/var/log/glusterfs> gluster_params:aux-gfid-mount acl> gluster_rundir:/var/run/gluster> glusterd_workdir:/var/lib/glusterd> gsyncd_miscdir:/var/lib/misc/gluster/gsyncd> ignore_deletes:false> isolated_slaves:> log_file:/var/log/glusterfs/geo-replication/> log_level:INFO> log_rsync_performance:trueAfter every batches records Rsync performance metrics in log file> master_disperse_count:1Not used now> master_distribution_count:2Not used now> master_replica_count:1Not used now> max_rsync_retries:10In case of rsync errors, maximum number of retries> meta_volume_mnt:/var/run/gluster/shared_storageIf meta volume is used for Active/Passive switching then the mount path.> pid_file:Path of Geo-rep worker PID file> remote_gsyncd:Path of remote_gsyncd. No need to change this since Geo-rep ssh connection uses proper path prefix in .ssh/authorized_keys file> replica_failover_interval:1In case of Active worker goes down, interval to make Passive worker becomes Active.> rsync_command:rsyncIf rsync command is not in PATH(rsync_command=/usr/local/bin/rsync)> rsync_opt_existing:trueAdds `?existing` to rsync command> rsync_opt_ignore_missing_args:trueAdds `--ignore-missing-args` to rsync command. Helps to avoid retries in case of file is deleted in Primary Volume at the time of syncing.> rsync_options:-hExtra Options to Rsync> rsync_ssh_options:Extra options to SSH command> slave_access_mount:falseSame as access_mount, for debugging purpose> slave_gluster_command_dir:/usr/sbinGluster command directory in remote nodes(Secondary volume)> slave_gluster_log_file:/var/log/glusterfs/geo-replication-slaves/Log dir path> slave_gluster_log_file_mbr:/var/log/glusterfs/geo-replication-slavesLog directory path in case of non-root Geo-replication> slave_gluster_log_level:INFOLog level for Gluster mounts done by Geo-rep process remote side.> slave_gluster_params:aux-gfid-mount aclParameters to Remote mount> slave_log_file:/var/log/glusterfs/geo-replication-slaves/Log file for Remote errors> slave_log_level:INFOLog level in remote side> slave_timeout:120SSH connections timeout> special_sync_mode:This is required to set during the failover> ssh_command:sshIf ssh command is not in PATH(ssh_command=/usr/local/sbin/ssh)> ssh_options:-oPasswordAuthentication=no -oStrictHostKeyChecking=no -i > /var/lib/glusterd/geo-replication/secret.pemIf any additional option to ssh command.> ssh_options_tar:-oPasswordAuthentication=no -oStrictHostKeyChecking=no > -i /var/lib/glusterd/geo-replication/tar_ssh.pemIf any additional option to tar + ssh command.> ssh_port:22SSH port for all SSH connection between Primary Volume to Secondary volume.> state_file:/var/lib/glusterd/geo-replication/Status file directory> state_socket_unencoded:Internal> stime_xattr_prefix:Internal> sync_acls:trueSync Posix Acls to remote volume.> sync_jobs:3Number of parallel rsync/tar processes to sync> sync_method:rsyncSupported sync methods are rsync and tarssh. rsync - After change detection, uses rsync to sync files. tarssh - After change detection, uses tar + ssh to sync files.> sync_xattrs:trueSame as use_rsync_xattrs, but it is having a known issue of not working in tarssh mode> tar_command:tarIn case tar command is not in Path(`tar_command=/usr/local/bin/tar`)> use_meta_volume:trueIn case of Replica bricks only one brick?s worker will be Active and participant in syncing. Other workers will be Passive and becomes active if the previously Active one goes down. With this option Geo-rep maintains a lock file in Meta Volume. Without this option, Geo-rep uses node uuid to detect Active/Passive.> use_rsync_xattrs:falseSync user created xattrs to remote volume.> working_dir:/var/lib/misc/gluster/gsyncd/?..Not Configurable, Working directory to store the processed changelog files.> > ________ > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://bluejeans.com/441850968 > > Gluster-users mailing list > Gluster-users at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-usersAravinda Vishwanathapura https://kadalu.io -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20201008/0a53f16f/attachment.html>