Gluster users - Jun 2017 - How to remove dead peer, osrry urgent again :(

On 11/06/2017 10:46 AM, WK wrote:
> I thought you had removed vna as defective and then ADDED in vnh as 
> the replacement?
>
> Why is vna still there? 
Because I *can't* remove it. It died, was unable to be brought up. The 
gluster peer detach command only works with live servers - A severe 
problem IMHO.

-- 
Lindsay Mathieson

On 6/10/2017 5:54 PM, Lindsay Mathieson wrote:
> On 11/06/2017 10:46 AM, WK wrote:
>> I thought you had removed vna as defective and then ADDED in vnh as 
>> the replacement?
>>
>> Why is vna still there? 
>
> Because I *can't* remove it. It died, was unable to be brought up. The 
> gluster peer detach command only works with live servers - A severe 
> problem IMHO.

wow, yes that is problematic.

I wonder if replace-brick would have handled that.

On Sun, 11 Jun 2017 at 06:25, Lindsay Mathieson <lindsay.mathieson at
gmail.com>
wrote:
> On 11/06/2017 10:46 AM, WK wrote:
> > I thought you had removed vna as defective and then ADDED in vnh as
> > the replacement?
> >
> > Why is vna still there?
>
> Because I *can't* remove it. It died, was unable to be brought up. The
> gluster peer detach command only works with live servers - A severe
> problem IMHO.

If the dead server doesn't host any volumes (bricks of volumes to be
specific) then you can actually remove the uuid entry from
/var/lib/glusterd from other nodes and restart glusterd instances one after
another as a workaround. With Glusterd2, we will see if we can have a
better user experience here.

GD2 team - your thoughts?



>
> --
> Lindsay Mathieson
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
-- 
- Atin (atinm)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170611/c68408a1/attachment.html>

On 11/06/2017 6:42 PM, Atin Mukherjee wrote:
> If the dead server doesn't host any volumes (bricks of volumes to be 
> specific) then you can actually remove the uuid entry from 
> /var/lib/glusterd from other nodes and restart glusterd instances one 
> after another as a workaround.
The server hosted a brick, but I removed that after it died with 
"gluster v remove-brick force". Does that mean I could edit glusterd
as
you suggest?

> With Glusterd2, we will see if we can have a better user experience here.

That would be good - I imagine in a lot of cases the only way a server 
is removed is *after* it has died.


Thanks.


-- 
Lindsay Mathieson

On 11/06/2017 6:42 PM, Atin Mukherjee wrote:
> If the dead server doesn't host any volumes (bricks of volumes to be 
> specific) then you can actually remove the uuid entry from 
> /var/lib/glusterd from other nodes 
Is that just the file entry in "/var/lib/glusterd/peers" ?


e.g I have:

    gluster peer status
    Number of Peers: 3

    Hostname: vnh.proxmox.softlog
    Uuid: 9eb54c33-7f79-4a75-bc2b-67111bf3eae7
    State: Peer in Cluster (Connected)

    *Hostname: vna.proxmox.softlog**
    **Uuid: de673495-8cb2-4328-ba00-0419357c03d7**
    **State: Peer in Cluster (Disconnected)**
    *
    Hostname: vnb.proxmox.softlog
    Uuid: 43a1bf8c-3e69-4581-8e16-f2e1462cfc36
    State: Peer in Cluster (Connected)

Do I just:

    rm /var/lib/glusterd/peers/de673495-8cb2-4328-ba00-0419357c03d7


On all the live nodes and restart glusterdd? nothing else?


thanks.

-- 
Lindsay Mathieson

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170611/ff47fceb/attachment.html>

On Sun, Jun 11, 2017 at 2:12 PM, Atin Mukherjee <amukherj at redhat.com>
wrote:
>
> On Sun, 11 Jun 2017 at 06:25, Lindsay Mathieson <
> lindsay.mathieson at gmail.com> wrote:
>
>> On 11/06/2017 10:46 AM, WK wrote:
>> > I thought you had removed vna as defective and then ADDED in vnh
as
>> > the replacement?
>> >
>> > Why is vna still there?
>>
>> Because I *can't* remove it. It died, was unable to be brought up.
The
>> gluster peer detach command only works with live servers - A severe
>> problem IMHO.
>
>
> If the dead server doesn't host any volumes (bricks of volumes to be
> specific) then you can actually remove the uuid entry from
> /var/lib/glusterd from other nodes and restart glusterd instances one after
> another as a workaround. With Glusterd2, we will see if we can have a
> better user experience here.
>
We can also do "gluster peer detach <hostname> force right?

>
> GD2 team - your thoughts?
>
>
>
>
>>
>> --
>> Lindsay Mathieson
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
> --
> - Atin (atinm)
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>


-- 
Pranith
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170612/797b335a/attachment.html>