[Gluster-users] Geo-Replication not detecting changes

[Jeremiah Rothschild]

Following up on my own thread...

I have spent hours and hours setting up, re-setting up, screwing with
undocumented variables, upgrading from LTS to non-LTS, etc etc.

Nothing seems to give.

This is very much an out-of-the-box setup and core functionality just isn't
working.

Can anyone throw me a bone here? Please? Do I file a bug for such an
open-ended issue? Is everyone assuming I've just screwed a step up? I must
say the documentation is pretty clear & simple. Do you want more logs?

If this is going to be a dead end then so be it but I at least need to make
sure I've tried my hardest to get a working deployment.

Thanks for your time and understanding!

j

On Thu, Mar 23, 2017 at 11:47:03AM -0700, Jeremiah Rothschild wrote:
> Hey all,
> 
> I have a vanilla geo-replication setup running. It is comprised of two
> servers, both CentOS 7 and GlusterFS 3.8.10:
> 
> * server1: Local server. Master volume named "foo".
> * server2: Remote server. Slave volume named "foo".
> 
> Everything went fine including the initial sync. However, no new changes are
> being seen or synced.
> 
> Geo-rep status looks clean:
> 
> # gluster volume geo-replication foo server2.franz.com::foo status
> MASTER NODE: server1.x.com
> MASTER VOL: foo
> MASTER BRICK: /gv0/foo
> SLAVE USER: root
> SLAVE NODE: server2.x.com::foo
> STATUS: Active
> CRAWL STATUS: Changelog Crawl
> LAST_SYNCED: 2017-03-23 10:12:57
> 
> In the geo-rep master log, I see these being triggered:
> 
> # tail -n3 foo/ssh%3A%2F%2Froot%401.2.3.4%3Agluster%3A%2F%2F127.0.0.1%3Afoo.log
> [2017-03-23 18:33:34.697525] I [master(/gv0/foo):534:crawlwrap] _GMaster: 20
> crawls, 0 turns
> [2017-03-23 18:34:37.441982] I [master(/gv0/foo):534:crawlwrap] _GMaster: 20
> crawls, 0 turns
> [2017-03-23 18:35:40.242851] I [master(/gv0/foo):534:crawlwrap] _GMaster: 20
> crawls, 0 turns
> 
> I don't see any errors in any of the other logs.
> 
> Not sure what else to poke at here. What are the possible values for the
> "change_detector" config variable? Would it be worthwhile to test with a
> method other than "changelog"? Other thoughts/ideas?
> 
> Thanks in advance!
> 
> j
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users