Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1450685

Summary:	Document options to configure geo-replication for lower latency
Product:	[Community] GlusterFS	Reporter:	nh2 <nh2-redhatbugzilla>
Component:	doc	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	bugs, nh2-redhatbugzilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-20 18:28:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description nh2 2017-05-14 16:33:30 UTC

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

Comment 1 Shyamsundar 2018-06-20 18:28:24 UTC

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.