[Bugs] [Bug 1802041] Peer is already being detached from cluster.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1802041

Sanju <srakonde at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(akshayvijapur at gma
                   |                            |il.com)



--- Comment #5 from Sanju <srakonde at redhat.com> ---
I see that even though the the node is in disconnected state, we are able to
detach it successfully.

[root at server4 glusterfs]# gluster pe s
Number of Peers: 3

Hostname: server3
Uuid: 3804f636-c89f-438e-94c0-c99f8e30eda9
State: Peer in Cluster (Disconnected)

Hostname: server1
Uuid: 5732298d-2c2a-4128-b8ad-1970094d4070
State: Peer in Cluster (Connected)

Hostname: server2
Uuid: 399973de-208e-4723-b66d-8119fca75d46
State: Peer in Cluster (Connected)
[root at server4 glusterfs]# gluster pe detach server3
All clients mounted through the peer which is getting detached need to be
remounted using one of the other active peers in the trusted storage pool to
ensure client gets notification on any changes done on the gluster
configuration and if the same has been done do you want to proceed? (y/n) y
peer detach: success
[root at server4 glusterfs]#

Please provide below information by running the following steps:
1. run get-state just before running peer detach command
2. run peer detach
3. run get-state just after running peer detach command

Share command-history.log, get-state output from originator and glusterd.log
from all the nodes.

Thanks,
Sanju

-- 
You are receiving this mail because:
You are on the CC list for the bug.