[Bugs] [Bug 1543706] glusterd fails to attach brick during restart of the node

bugzilla at redhat.com bugzilla at redhat.com
Fri Feb 9 03:40:09 UTC 2018


Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |POST
           Assignee|bugs at gluster.org            |amukherj at redhat.com

--- Comment #2 from Atin Mukherjee <amukherj at redhat.com> ---
Description of problem:
In a 3 node cluster with brick multiplexing is enabled, when one of the node is
down and a volume goes through some option changes through volume set, on
reboot of the node all the bricks fail to attach and hence looses the brick
multiplexing feature. And other observation is the entire handshake process
becomes very very slow and can take even hours and in between if some one
brings down glusterd then we're going to loose certain volume info files.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a 3 node cluster, enable brick multiplexing and setup 20 1 X 3
volumes and start them.
2. Now bring down glusterd on first node and perform volume set operation for
all 20 volumes from any of the other nodes.
3. bring back glusterd instance on 1st node.

Actual results:
Bricks failed to attach and multiplexing mode is lost. And handshake becomes
damn slow.

Expected results:
Bricks should come up in a multiplexed mode.

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list