Bug 1526371
Summary: | clean up port map on brick disconnect | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sunil Kumar Acharya <sheggodu> | |
Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
Status: | CLOSED ERRATA | QA Contact: | Ambarish <asoman> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.3 | CC: | 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
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 |