Bug 1026831
Summary: | Dist-geo-rep : In the newly added node, the gsyncd uses xsync as change_detector instead of changelog, | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vijaykumar Koppad <vkoppad> |
Component: | geo-replication | Assignee: | Aravinda VK <avishwan> |
Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.1 | CC: | aavati, annair, avishwan, csaba, david.macdonald, rhinduja |
Target Milestone: | --- | ||
Target Release: | RHGS 3.1.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | consistency | ||
Fixed In Version: | glusterfs-3.7.0-2.el6rhs | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-29 04:29:24 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: | |||
Bug Depends On: | |||
Bug Blocks: | 987980, 1032445, 1202842, 1223636 |
Description
Vijaykumar Koppad
2013-11-05 13:57:31 UTC
Verified with the build: glusterfs-3.7.1-10.el6rhs.x86_64 When new node was added, it tried history which fails because no changelog is present. It then did perform the xsync and once the xsync is successful, it set the stime and used the changelog as change detector. [2015-07-16 17:10:59.505544] I [master(/rhs/brick2/b2):528:crawlwrap] _GMaster: crawl interval: 1 seconds [2015-07-16 17:10:59.510324] I [master(/rhs/brick1/b1):528:crawlwrap] _GMaster: crawl interval: 1 seconds [2015-07-16 17:10:59.541496] I [master(/rhs/brick2/b2):1123:crawl] _GMaster: starting history crawl... turns: 1, stime: (-1, 0) [2015-07-16 17:10:59.541810] I [master(/rhs/brick2/b2):1126:crawl] _GMaster: stime not available, abandoning history crawl [2015-07-16 17:10:59.542121] I [resource(/rhs/brick2/b2):1444:service_loop] GLUSTER: No stime available, using xsync crawl [2015-07-16 17:10:59.550285] I [master(/rhs/brick2/b2):519:crawlwrap] _GMaster: primary master with volume id 61887764-6ecb-4956-bf10-0cae54b8f497 ... [2015-07-16 17:10:59.562691] I [master(/rhs/brick2/b2):528:crawlwrap] _GMaster: crawl interval: 60 seconds [2015-07-16 17:10:59.577857] I [master(/rhs/brick2/b2):1230:crawl] _GMaster: starting hybrid crawl..., stime: (-1, 0) [2015-07-16 17:10:59.586750] I [master(/rhs/brick2/b2):1237:crawl] _GMaster: finished hybrid crawl syncing, stime: (1437046859, 0) [2015-07-16 17:10:59.591370] I [master(/rhs/brick2/b2):519:crawlwrap] _GMaster: primary master with volume id 61887764-6ecb-4956-bf10-0cae54b8f497 ... [2015-07-16 17:10:59.597722] I [master(/rhs/brick2/b2):528:crawlwrap] _GMaster: crawl interval: 3 seconds [2015-07-16 17:11:02.645987] I [master(/rhs/brick2/b2):1084:crawl] _GMaster: slave's time: (1437046859, 0) [2015-07-16 17:11:59.808649] I [master(/rhs/brick1/b1):541:crawlwrap] _GMaster: 0 crawls, 0 turns [2015-07-16 17:12:00.626524] I [master(/rhs/brick2/b2):541:crawlwrap] _GMaster: 20 crawls, 1 turns [2015-07-16 17:13:00.102729] I [master(/rhs/brick1/b1):541:crawlwrap] _GMaster: 0 crawls, 0 turns This is expected in 3.1. Moving this bug to verified state. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html |