Red Hat Bugzilla – Bug 986885
Dist-geo-rep : geo-rep cascading is broken and intermediate master says master is corrupt
Last modified: 2014-08-24 20:50:12 EDT
Description of problem: Geo-rep cascading setup will faulty at intermediate master and the geo-rep logs at intermediate master says,
[2013-07-22 15:44:28.378478] I [master(/bricks/brick1):500:crawlwrap] _GMaster: crawl interval: 60 seconds
[2013-07-22 15:44:28.489165] E [syncdutils(/bricks/brick1):184:log_raise_exception] <top>: master is corrupt
[2013-07-22 15:44:28.489896] I [syncdutils(/bricks/brick1):158:finalize] <top>: exiting.
Version-Release number of selected component (if applicable):220.127.116.11rhs.beta5-2.el6rhs.x86_64
How reproducible:Happens everytime
Steps to Reproduce:
1.create 3 clusters, master, imaster and slave
2.create and start a geo-rep session between master and imaster.
3.Then create a geo-rep session between imaster and slave.
4.After creating geo-rep between imaster and slave, imaster become intermediate master.
5.Check geo-rep status ate intermediate master.
Actual results:Intermediate master status will be faulty and log says master is corrupt.
Expected results: Intermediate master status should stable.
verified in glusterfs-18.104.22.168rhs.beta6-1
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.