Bug 1215114 - gluster peer probe hangs
Summary: gluster peer probe hangs
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.5.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-24 10:49 UTC by alex
Modified: 2016-06-17 15:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-06-17 15:57:32 UTC
Regression: ---
Mount Type: fuse
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
gfs1 and gfs3 debug logging (250.01 KB, text/plain)
2015-04-24 10:49 UTC, alex
no flags Details

Description alex 2015-04-24 10:49:37 UTC
Created attachment 1018395 [details]
gfs1 and gfs3 debug logging

Initial data:
All nodes have the same:
1) os distribution (proxmox v3.3, kernel 2.6.32-32-pve)
2) disabled selinux
3) default iptables with ALLOW action
4) version of glusterfs
      - ii  glusterfs-client                 3.5.2-1
      - ii  glusterfs-common                 3.5.2-1
      - ii  glusterfs-server                 3.5.2-1
5) correct and working DNS forward and reverse resolution

6) 
192.168.9.53/gfs3 \ 
192.168.9.54/gfs4  - already in cluster
192.168.9.56/gfs6 /

192.168.9.51/gfs1 - want to add to the cluster
192.168.9.52/gfs2 - want to add to the cluster

gfs1 and gfs2 previously were part of another glusterfs cluster, but I stopped all services and removed /var/lib/glusterd directory.

7) cluster contains several production distributed-replicated volumes

Description of problem: 
When I do gluster peer probe gfs1 or gfs2 from any node in the cluster the command hangs and after timeout new peer has status "Probe Sent to Peer":
gfs3#gluster peer status
Number of Peers: 3

Hostname: gfs6
Uuid: 6bd6ee25-e257-4703-b500-330741b90471
State: Peer in Cluster (Connected)

Hostname: gfs4
Uuid: bb1bed20-25bf-43b0-8faa-49f1b5b9ae59
State: Peer in Cluster (Connected)

Hostname: gfs1
Uuid: c5cd8152-c239-474a-977b-9c6b35edd857
State: Probe Sent to Peer (Connected) 

-- gfs3 added peer gfs1 ------------
gfs3#cat /var/lib/glusterd/peers/c5cd8152-c239-474a-977b-9c6b35edd857
uuid=c5cd8152-c239-474a-977b-9c6b35edd857
state=1
hostname1=gfs1

-- but gfs1 did not add gfs3
gfs1#cat /var/lib/glusterd/peers/192.168.9.53
uuid=00000000-0000-0000-0000-000000000000
state=8
hostname1=192.168.9.53


Debug logging showed that gfs3 sent req, gfs1 sent resp, gfs3 received response and after that gfs3 does not do anything until command timeouts (see attach).
So gfs3 does not complete peer handshake with gfs1.

Comment 1 Niels de Vos 2016-06-17 15:57:32 UTC
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.


Note You need to log in before you can comment on or make changes to this bug.