Bug 1526371

Summary: clean up port map on brick disconnect
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Sunil Kumar Acharya <sheggodu>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED ERRATA QA Contact: Ambarish <asoman>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: amukherj, asoman, asriram, nchilaka, nerawat, rcyriac, rhinduja, rhs-bugs, sasundar, srmukher, storage-qa-internal, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.3.1 Async   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-52.1 Doc Type: Bug Fix
Doc Text:
The portmap entry allocation that glusterd maintains for each of its brick is cleaned up on a graceful shutdown of the respective brick processes. In case a brick process was killed through SIGKILL signal or crashed, glusterd will not clean up the respective portmap entry allocation and after restarting the same brick glusterd may end up having two portmap allocations for the same brick.glusterd reports with a stale port to the client, resulting failure in connection. With this fix, the stale port entry is removed even for a brick crash or SIGKILL event of a brick process. The client now successfully connects to the brick after the brick is restarted.
Story Points: ---
Clone Of: 1503244
: 1530512 (view as bug list) Environment:
Last Closed: 2018-01-11 02:46:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1503244, 1503246, 1507747, 1507749    
Bug Blocks: 1530512    

Comment 8 Ambarish 2018-01-03 08:37:29 UTC
Unable to reproduce the issue on 331_async.


**TEST STEPS** :





[root@gqas001 /]# ps -ef|grep glus
root       515     1  0 07:30 ?        00:00:00 /usr/sbin/glusterfsd -s gqas001.sbu.lab.eng.bos.redhat.com --volfile-id butcher.gqas001.sbu.lab.eng.bos.redhat.com.bricks1-A1 -p /var/run/gluster/vols/butcher/gqas001.sbu.lab.eng.bos.redhat.com-bricks1-A1.pid -S /var/run/gluster/6a74476cb867d30c8ccbb3fb03bc5141.socket --brick-name /bricks1/A1 -l /var/log/glusterfs/bricks/bricks1-A1.log --xlator-option *-posix.glusterd-uuid=0ea806f4-e798-4daf-8c3b-8891002b3839 --brick-port 49153 --xlator-option butcher-server.listen-port=49153
root       538     1  0 07:30 ?        00:00:00 /usr/sbin/glusterfs -s localhost --volfile-id gluster/glustershd -p /var/run/gluster/glustershd/glustershd.pid -l /var/log/glusterfs/glustershd.log -S /var/run/gluster/5d88e7a8c6588a66bceee8180ced8795.socket --xlator-option *replicate*.node-uuid=0ea806f4-e798-4daf-8c3b-8891002b3839
root       604 26054  0 07:30 pts/0    00:00:00 grep --color=auto glus
root     32103     1  0 07:19 ?        00:00:00 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO
[root@gqas001 /]# 
[root@gqas001 /]# 

[root@gqas001 /]# 
[root@gqas001 /]# 
[root@gqas001 /]# kill -9 515
[root@gqas001 /]# 

[root@gqas001 /]# 
[root@gqas001 /]# gluster v start butcher force
volume start: butcher: success
[root@gqas001 /]# 



[root@gqas001 /]# ps -ef|grep glus
root       648     1  0 07:31 ?        00:00:00 /usr/sbin/glusterfsd -s gqas001.sbu.lab.eng.bos.redhat.com --volfile-id butcher.gqas001.sbu.lab.eng.bos.redhat.com.bricks1-A1 -p /var/run/gluster/vols/butcher/gqas001.sbu.lab.eng.bos.redhat.com-bricks1-A1.pid -S /var/run/gluster/6a74476cb867d30c8ccbb3fb03bc5141.socket --brick-name /bricks1/A1 -l /var/log/glusterfs/bricks/bricks1-A1.log --xlator-option *-posix.glusterd-uuid=0ea806f4-e798-4daf-8c3b-8891002b3839 --brick-port 49152 --xlator-option butcher-server.listen-port=49152
root       670     1  0 07:31 ?        00:00:00 /usr/sbin/glusterfs -s localhost --volfile-id gluster/glustershd -p /var/run/gluster/glustershd/glustershd.pid -l /var/log/glusterfs/glustershd.log -S /var/run/gluster/5d88e7a8c6588a66bceee8180ced8795.socket --xlator-option *replicate*.node-uuid=0ea806f4-e798-4daf-8c3b-8891002b3839
root       735 26054  0 07:31 pts/0    00:00:00 grep --color=auto glus
root     32103     1  0 07:19 ?        00:00:00 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO
[root@gqas001 /]# 



Moving to Verified.

Comment 11 errata-xmlrpc 2018-01-11 02:46:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0083