Bug 1526368 - Brick Multiplexing: stale brick processes getting created and volume status shows brick as down(pkill glusterfsd glusterfs ,glusterd restart)
Summary: Brick Multiplexing: stale brick processes getting created and volume status s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Atin Mukherjee
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard: brick-multiplexing
Depends On: 1505363 1506513 1508283
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-15 09:55 UTC by Sunil Kumar Acharya
Modified: 2018-01-18 11:22 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8.4-52.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1505363
Environment:
Last Closed: 2018-01-11 02:46:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0083 0 normal SHIPPED_LIVE glusterfs bug fix update 2018-01-11 07:46:21 UTC

Comment 4 Nag Pavan Chilakam 2017-12-28 13:26:40 UTC 
have tried the scenario thrice and didn't see any stale processes.
However I did see cluster.max-bricks-per-process not being honored
hence raised a seperate bug to track the same 
BZ#1529514 - Brick Multiplexing:cluster.max-bricks-per-process not honored(more bricks being attached to glusterfsd) when we do a restart of bricks and glusterd (pkill glusterfsd glusterfs ,glusterd restart)
Comment 5 Nag Pavan Chilakam 2017-12-28 13:27:12 UTC 
moved the bug to verified based on comment#4
Comment 8 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
Note You need to log in before you can comment on or make changes to this bug.