[Gluster-users] Impact of force option in remove-brick

[Gaurav Garg]

comment inline.

----- Original Message -----
From: "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com>
To: "Gaurav Garg" <ggarg at redhat.com>
Cc: gluster-users at gluster.org, gluster-devel at gluster.org
Sent: Tuesday, March 22, 2016 12:23:25 PM
Subject: Re: [Gluster-users] Impact of force option in remove-brick

On Tue, Mar 22, 2016 at 12:14 PM, Gaurav Garg <ggarg at redhat.com> wrote:

> >> 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
>
>
> remove-brick without force option will perform task based on your option,
> for eg. remove-brick start option will start migration of file from given
> remove-brick to other available bricks in the cluster. you can check status
> of this remove-brick task by issuing remove-brick status command.
>
> But remove-brick with force option will just forcefully remove brick from
> the cluster.
> It will result in data loss in case of distributed volume, because it will
> not migrate file
> from given remove-brick to other available bricks in the cluster. In case
> of replicate volume
> you might not have problem by doing remove-brick force because later on
> after adding brick you
> can issue heal command and migrate file from first replica set to this
> newly added brick.\
>

so when you are saying the forcefully remove the brick means it will remove
the brick even when
that brick is not available or available but have the different uuid of
peers, without generating any error?


yes, it will remove the brick when brick is not available (brick not available
means when brick is hosted on the node which is down or not available).

i didn't get your point how are you getting different uuid of peers.

~Gaurav

>
> Thanks,
>
> ~Gaurav
>
> ----- Original Message -----
> From: "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com>
> To: gluster-users at gluster.org, gluster-devel at gluster.org
> Sent: Tuesday, March 22, 2016 11:35:52 AM
> Subject: [Gluster-users] Impact of force option in remove-brick
>
> 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.
> 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.
>
> 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
>
>
> Regards
> Abhishek
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>



-- 




Regards
Abhishek Paliwal