Gluster users - Mar 2019 - cannot add server back to cluster after reinstallation

On Wed, 27 Mar 2019 at 15:24, Riccardo Murri <riccardo.murri at gmail.com>
wrote:
> I managed to put the reinstalled server back into connected state with
> this procedure:
>
> 1. Run `for other_server in ...; do gluster peer probe $other_server;
> done` on the reinstalled server
> 2. Now all the peers on the reinstalled server show up as "Accepted
> Peer Request", which I fixed with the procedure outlined in the last
> paragraph of
>
https://docs.gluster.org/en/v3/Troubleshooting/troubleshooting-glusterd/#debugging-glusterd
>
> Can anyone confirm that this is a good way to proceed and I won't be
> heading quickly towards corrupting volume data?

Check cluster.op-version, peer status, volume status output. If they are
all fine you?re good.

>
> Thanks,
> Riccardo
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
-- 
--Atin
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190327/1396ce67/attachment.html>

Hello Atin,
> Check cluster.op-version, peer status, volume status output. If they are
all fine you?re good.
Both `op-version` and `peer status` look fine:
```
# gluster volume get all cluster.max-op-version
Option                                  Value
------                                  -----
cluster.max-op-version                  31202

# gluster peer status
Number of Peers: 4

Hostname: glusterfs-server-004
Uuid: 9a5763d2-1941-4e5d-8d33-8d6756f7f318
State: Peer in Cluster (Connected)

Hostname: glusterfs-server-005
Uuid: d53398f6-19d4-4633-8bc3-e493dac41789
State: Peer in Cluster (Connected)

Hostname: glusterfs-server-003
Uuid: 3c74d2b4-a4f3-42d4-9511-f6174b0a641d
State: Peer in Cluster (Connected)

Hostname: glusterfs-server-001
Uuid: 60bcc47e-ccbe-493e-b4ea-d45d63123977
State: Peer in Cluster (Connected)
```

However, `volume status` shows a missing snapshotd on the reinstalled
server (the 002 one).
We're not using snapshots so I guess this is fine too?

```
# gluster volume status
Status of volume: glusterfs
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick glusterfs-server-005:/s
rv/glusterfs                                49152     0          Y       1410
Brick glusterfs-server-004:/s
rv/glusterfs                                49152     0          Y       1416
Brick glusterfs-server-003:/s
rv/glusterfs                                49152     0          Y       1520
Brick glusterfs-server-001:/s
rv/glusterfs                                49152     0          Y       1266
Brick glusterfs-server-002:/s
rv/glusterfs                                49152     0          Y       3011
Snapshot Daemon on localhost                N/A       N/A        Y       3029
Snapshot Daemon on glusterfs-
server-001                                  49153     0          Y       1361
Snapshot Daemon on glusterfs-
server-005                                  49153     0          Y       1478
Snapshot Daemon on glusterfs-
server-004                                  49153     0          Y       1490
Snapshot Daemon on glusterfs-
server-003                                  49153     0          Y       1563

Task Status of Volume glusterfs
------------------------------------------------------------------------------
Task                 : Rebalance
ID                   : 0eaf6ad1-df95-48f4-b941-17488010ddcc
Status               : failed
```

Thanks,
Riccardo