[Bugs] [Bug 1506513] stale brick processes getting created and volume status shows brick as down (pkill glusterfsd glusterfs , glusterd restart)

bugzilla at redhat.com bugzilla at redhat.com
Thu Oct 26 09:19:31 UTC 2017


Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
            Summary|Brick Multiplexing: stale   |stale brick processes
                   |brick processes getting     |getting created and volume
                   |created and volume status   |status shows brick as
                   |shows brick as down(pkill   |down(pkill glusterfsd
                   |glusterfsd glusterfs        |glusterfs ,glusterd
                   |,glusterd restart)          |restart)

--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
On a brick multiplexing 3 node cluster setup, having 12 1 X 3 volumes and
restarting all the gluster processes leaves up with some of brick status
showing offline.

Steps to Reproduce:
1.brick mux enabled, max brick per process set to 3
2.had about 12 volumes,about 10 were 1x3 and 2 were 2x2 =>in total 17 bricks
per node
3.did a pkill glusterfsd, glusterfs and service glusterd stop
4. did service glusterd start

Actual results:
found about 11-18(different tries, different numbers) glusterfsd running, while
only 7 are supposed to be created

also volume status shows bricks as offline for some of them

however, no IO impact

We would hit this in upgrade path

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