[Gluster-users] geo-replication delay?

[James Le Cuirot]

Hi Venky,

> On Wed, May 7, 2014 at 11:07 PM, Venky Shankar
> <yknev.shankar at gmail.com>wrote:
> >
> > On Wed, May 7, 2014 at 6:10 PM, James Le Cuirot
> > <chewi at aura-online.co.uk>wrote:
> >
> >> I have set up geo-replication between two machines on my LAN for
> >> testing. Both are using NTP and the clocks are definitely in sync.
> >> CRAWL STATUS reports Changelog Crawl. When I make a change on the
> >> master, it takes up to a minute (sometimes less) for the slave to
> >> notice.
> >
> > ​That's because the change​ detection interval is 60 seconds by
> > default[1] in 3.5. This has been changed to 15 seconds lately.

I have a very bad habit of needing things that haven't quite been
released yet. ;)

> >> Now I understand that geo-replication will always have some delay,
> >> not least because it is asynchronous, but given these are tiny
> >> changes with practically no other activity going on, I was
> >> expecting it to be a little more responsive. Even in production,
> >> there will very little traffic so some additional resource usage
> >> to speed things up would not be an issue. Is this configurable at
> >> all?
> >
> > ​It's configurable. Try this:
> >
> > # gluster volume set <volume> rollover-time 1
> >
> > to indentify changes (followed by syncing it to the slave) every
> > second. This will definitely speed up replication.

Fantastic! I just tried it and it works a charm. Many thanks. :)

Regards,
James