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@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
