Bug 1450684 - Geo-replication delay cannot be configured to less than 3 seconds
Summary: Geo-replication delay cannot be configured to less than 3 seconds
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-14 16:29 UTC by nh2
Modified: 2018-06-20 18:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:26:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description nh2 2017-05-14 16:29:08 UTC
Description of problem (on gluster 3.10.1):

It is impossible to configure geo-replication so that replication has low latency, even on links that have < 1ms latency.

Questions on how to improve the latency have come up in the past, for example:
http://lists.gluster.org/pipermail/gluster-users/2014-May/017272.html

Setting the volume option `rollover-time 1` improves the situation (it defaults to 15 seconds delay), but is not fully satisfying, as it can still take up to 3 seconds for a change to be reflected on replication slaves.

This is because gsyncd.py has an option

  op.add_option('--change-interval', metavar='SEC', type=int, default=3)

that defaults to 3 seconds and is not configurable from by the user.

Please make this setting configurable, so that users can set up low-latency geo replication.

Comment 1 Shyamsundar 2018-06-20 18:26:30 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.


Note You need to log in before you can comment on or make changes to this bug.