[Gluster-users] Explanation of gluster vol geo-repliation options
aravinda at kadalu.io
Thu Oct 8 06:37:43 UTC 2020
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
> but i am wondering if there is a more detailed explanation of all the
> other options listed below.
> Thanks in advance.
Internal 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.
Use 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.
Changelogs rollover interval
Processed changelogs will be stored in working directory partitioned by the specified format.
Bytes to limit the changelogs in Batches. Mostly useful if backlog to sync is more.
Changelogs processing log files directory
Changelogs processing log level
Time will be set here when checkpoint command is run.
CLI Log file path
CLI log level
Geo-rep Working dir to store config, status etc
This enables automatic resolution to GFID conflicts in Secondary Volume.
Geo-rep runs Gluster CLI when needed, any extra options can be provided using this.
If command name is different.
If gluster command is not in PATH(gluster_command_dir=/usr/local/sbin)
Gluster mount(Mounted by Geo-rep process) log directory
Gluster mount(Mounted by Geo-rep process) log level
> gluster_params:aux-gfid-mount acl
After every batches records Rsync performance metrics in log file
Not used now
Not used now
Not used now
In case of rsync errors, maximum number of retries
If meta volume is used for Active/Passive switching then the mount path.
Path of Geo-rep worker PID file
Path of remote_gsyncd. No need to change this since Geo-rep ssh connection uses proper path prefix in .ssh/authorized_keys file
In case of Active worker goes down, interval to make Passive worker becomes Active.
If rsync command is not in PATH(rsync_command=/usr/local/bin/rsync)
Adds `—existing` to rsync command
Adds `--ignore-missing-args` to rsync command. Helps to avoid retries in case of file is deleted in Primary Volume at the time of syncing.
Extra Options to Rsync
Extra options to SSH command
Same as access_mount, for debugging purpose
Gluster command directory in remote nodes(Secondary volume)
Log dir path
Log directory path in case of non-root Geo-replication
Log level for Gluster mounts done by Geo-rep process remote side.
> slave_gluster_params:aux-gfid-mount acl
Parameters to Remote mount
Log file for Remote errors
Log level in remote side
SSH connections timeout
This is required to set during the failover
If ssh command is not in PATH(ssh_command=/usr/local/sbin/ssh)
> ssh_options:-oPasswordAuthentication=no -oStrictHostKeyChecking=no -i
If any additional option to ssh command.
> ssh_options_tar:-oPasswordAuthentication=no -oStrictHostKeyChecking=no
> -i /var/lib/glusterd/geo-replication/tar_ssh.pem
If any additional option to tar + ssh command.
SSH port for all SSH connection between Primary Volume to Secondary volume.
Status file directory
Sync Posix Acls to remote volume.
Number of parallel rsync/tar processes to sync
Supported 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.
Same as use_rsync_xattrs, but it is having a known issue of not working in tarssh mode
In case tar command is not in Path(`tar_command=/usr/local/bin/tar`)
In 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.
Sync user created xattrs to remote volume.
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users