Bug 1437244
Summary: | geo-rep not detecting changes | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | jeremiah | ||||||||||||||
Component: | geo-replication | Assignee: | Pranith Kumar K <pkarampu> | ||||||||||||||
Status: | CLOSED EOL | QA Contact: | |||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 3.10 | CC: | bugs, dimitri.ars, jeremiah, wattersm | ||||||||||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||
OS: | Linux | ||||||||||||||||
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:26:22 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: | |||||||||||||||||
Attachments: |
|
Description
jeremiah
2017-03-29 21:30:54 UTC
Created attachment 1267436 [details]
Master volume log 1
Created attachment 1267437 [details]
Master volume log 2
Created attachment 1267438 [details]
Master volume log 3
Created attachment 1274471 [details]
Updated master log 1
Here's the new batch of log files, they don't have any of the 'transport end point not connected' errors in them anymore.
Created attachment 1274472 [details]
Updated master log 2
Created attachment 1274473 [details]
Updated master log 3
I've also just noticed this issue. geo-replication is working according to the status output however the data on my slave nodes does *not* match what is on the master volume. [root@mdct-gluster-srv1 ~]# gluster volume geo-replication gv0 status MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- mdct-gluster-srv1 gv0 /var/mnt/gluster/brick2 root ssh://mdct-gluster-srv3::slavevol mdct-gluster-srv3 Active Changelog Crawl 2017-04-28 08:35:58 mdct-gluster-srv2 gv0 /var/mnt/gluster/brick root ssh://mdct-gluster-srv3::slavevol mdct-gluster-srv3 Passive N/A N/A mdct-gluster-srv1 gv0 /var/mnt/gluster/brick2 root ssh://mdct-gluster-srv4::slavevol mdct-gluster-srv4 Active Changelog Crawl 2017-04-28 08:35:58 mdct-gluster-srv2 gv0 /var/mnt/gluster/brick root ssh://mdct-gluster-srv4::slavevol mdct-gluster-srv4 Passive N/A N/A ls shows different data as show below. [root@mdct-00fs-cent7 ~]# ls /var/mnt/shadow/pub/fedora/ dart releases updates [root@mdct-00fs-cent7 ~]# ls /var/mnt/gluster2/pub/fedora/ 20 21 22 24 25 dart README releases updates /var/mnt/shadow is the master volume. 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. |