Bug 1291974
Summary: | [GlusterD]: Bricks are in offline state after node reboot | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Byreddy <bsrirama> |
Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> |
Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.1 | CC: | amukherj, asrivast, nlevinki, rhinduja, vbellur |
Target Milestone: | --- | ||
Target Release: | RHGS 3.3.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.8.4-19 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-21 04:25:52 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: | |||
Bug Blocks: | 1417147 |
Description
Byreddy
2015-12-16 05:41:24 UTC
We actually debugged this issue in a set up where we identified that the moment glusterd started the brick(s), immediately it received disconnect event from the brick. Post that rpc_reconnect () fails after every 3 seconds because the underlying socket is already connected, this looks weird but that's what we got to know from the state of these layers. During this, we also identified a place in glusterd code where we are not handling the rpc connection in a right way (in terms of (un)setting the connected flag). I've posted a patch [1] upstream, however having said that the patch doesn't solve the entire problem. So the RCA is still unknown. [1] http://review.gluster.org/#/c/12908/ Byreddy, As communicated, can you try your luck to get to a reproducer? I think this is now fixed through BZ 1385605. BUILD : 3.8.4-35 After node reboot, bricks are online. In RHSC Setup, bricks are online when one of the node is in maintenance state as expected. Hence marking the bug as verified 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-2017:2774 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-2017:2774 |