Red Hat Bugzilla – Bug 861945
if replace-brick is running , it shouldn't allow geo-rep to start.
Last modified: 2014-08-24 20:49:52 EDT
Description of problem: Currently, if there is a geo-rep session going on , we don't allow replace-brick to start or do any replace-brick operations. Similarly , we shouldn't allow geo-rep to start if there is a replace-brick going on.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1.Create a volume, lets say distribute-volume,
2.Create fair amount of data on the mount point.
3.Start replace-brick of one of the volume
4.Before repace-brick commit, try to start geo-rep.
Actual results: It allow geo-rep to start
Expected results: IT shouldn't allow replace-brick to start
CHANGE: http://review.gluster.org/4289 (gsyncd / geo-rep: do not start geo-rep if replace brick is in progress) merged in master by Anand Avati (firstname.lastname@example.org)
Verified on 188.8.131.52rhs-1.el6rhs.x86_64
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.