[Bugs] [Bug 1223634] New: glusterd could crash in remove-brick-status when local remove-brick process has just completed
bugzilla at redhat.com
bugzilla at redhat.com
Thu May 21 05:35:02 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1223634
Bug ID: 1223634
Summary: glusterd could crash in remove-brick-status when local
remove-brick process has just completed
Product: GlusterFS
Version: 3.7.0
Component: glusterd
Assignee: kparthas at redhat.com
Reporter: kparthas at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Depends On: 1223338
Blocks: 1219955 (glusterfs-3.7.1)
+++ This bug was initially created as a clone of Bug #1223338 +++
Description of problem:
Glusterd process could crash while executing remove-brick-status command around
the time when the local remove-brick process (i.e, rebalance process) has
completed migrating data.
Version-Release number of selected component (if applicable):
mainline
How reproducible:
Intermittent
Steps to Reproduce:
1. Create and start a volume.
2. Add files/directories as required.
3. Remove one or more bricks using remove-brick-start command.
4. Issue remove-brick-status command around the time when the local
remove-brick
process is completed.
Actual results:
glusterd process crashes.
Expected results:
glusterd shouldn't crash. It would be helpful if the remove-brick-status
command failed saying that the rebalance process may have just completed with
migration of data from the bricks being removed.
Additional info:
The above steps are representative of when the issue can be seen but not really
helpful if you wish to automate this. The following link leads to the
regression test, as part of GlusterFS regression test suite, that has hit this
problem more often. This could help those interested in automation.
https://github.com/gluster/glusterfs/blob/master/tests/bugs/glusterd/bug-974007.t
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1219955
[Bug 1219955] GlusterFS 3.7.1 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1223338
[Bug 1223338] glusterd could crash in remove-brick-status when local
remove-brick process has just completed
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=SDYo6Uh9Tf&a=cc_unsubscribe
More information about the Bugs
mailing list