Description of problem (on gluster 3.10.1): With default settings, geo-replication has very high latency, about 15 seconds until a change done to a master appears on a replication slave. The key setting to control this delay is `rollover-time`. This setting is not documented in glusterfs docs; I could only find it via mailing list replies and in the Troubleshooting section of RedHat Storage: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/sect-Troubleshooting_Geo-replication.html. Please add the relevant settings to the docs, and also a section in the geo-replication docs to give hints on how latency can be improved. Also relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1450684
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.