[Gluster-users] Impact of force option in remove-brick
amukherj at redhat.com
Tue Mar 22 06:40:38 UTC 2016
On 03/22/2016 11:35 AM, ABHISHEK PALIWAL wrote:
> Hi Team,
> I have the following scenario:
> 1. I have one replica 2 volume in which two brick are available.
> 2. in such permutation and combination I got the UUID of peers mismatch.
You *should not* get UUID mismatches and if you happen to get into that
situation your cluster is messed up and remove brick wouldn't work.
> 3. Because of UUID mismatch when I tried to remove brick on the second
> board I am getting the Incorrect Brick failure.
> Now, I have the question if I am using the remove-brick command with the
> 'force' option it means it should remove the brick in any situation
> either the brick is available or its UUID is mismatch.
UUID is the source of information by which all our configuration is
managed. If UUID has gone for a toss then there is no way that glusterd
can pick up the right brick. So here this question of difference between
remove brick and remove brick force really doesn't matter.
> I just want to know what is the difference in the following scenario:
> 1. remove-brick without the force option
> 2. remove-brick with the force option
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users