[Gluster-users] Help, peer probe seems to get stuck on large cluster.

Vijay Bellur vbellur at redhat.com
Tue Sep 1 08:18:21 UTC 2015


On Tuesday 01 September 2015 09:10 AM, Yiping Peng wrote:
> Even if I'm seeing disconnected nodes (also from already-in-pool nodes),
> my volume is still intact and available. So I'm guessing that glusterd
> has few to do with volume/brick service?
> Am I safe to kill all glusterd on all servers and start this whole peer
> probing process all over again?
> If I do this, will the currently mounted volumes become unavailable?
>

glusterd is the management daemon that takes care of cluster membership 
& configuration primarily.Normally a glusterd restart would not be 
needed to resolve the disconnected nodes' problem.

A few questions:

Is this setup on bare metal or does it involve virtual machines?

Have you checked if port 24007 is reachable on all peers?

Additionally, if you are not running 3.7.3 you would need to ensure that 
the privileged ports check is bypassed in all glusterds.

Regards,
Vijay



More information about the Gluster-users mailing list