Bug 1006247
Summary: | Rebalance Status message not showing correct status . | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Kaushal <kaushal> |
Component: | glusterd | Assignee: | Kaushal <kaushal> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4.0 | CC: | gluster-bugs, kaushal, rhs-bugs, sabose, senaik, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.5.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 982104 | Environment: | |
Last Closed: | 2014-04-17 11:47:36 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: | 982104 |
Description
Kaushal
2013-09-10 10:02:28 UTC
REVIEW: http://review.gluster.org/5895 (glusterd: Reset rebalance task on add-brick) posted (#1) for review on master by Kaushal M (kaushal) REVIEW: http://review.gluster.org/5895 (glusterd: Don't reset rebalance status on add-brick) posted (#2) for review on master by Kaushal M (kaushal) REVIEW: http://review.gluster.org/5895 (glusterd: Don't reset rebalance status on add-brick) posted (#3) for review on master by Kaushal M (kaushal) COMMIT: http://review.gluster.org/5895 committed in master by Anand Avati (avati) ------ commit 67c28b19355c47e96d1420405cc38753a3e5f9be Author: Kaushal M <kaushal> Date: Tue Sep 10 15:33:00 2013 +0530 glusterd: Don't reset rebalance status on add-brick The rebalance status was being reset to 'Not started' when add-brick was performed. This would lead to odd cases where a 'rebalance status' on a volume would show status as 'not started' but would also include the rebalance statistics. This also affected the showing of asynchronus task status in 'volume status' command. By not resetting the status prevent the above issues from happening. Since we use the running/not-running of the rebalance process as the check when performing other operations we can safely leave the rebalance stats collected on an add-brick. Change-Id: I4c69d9c789d081c6de7e7a81dd0d4eba2e83ec17 BUG: 1006247 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/5895 Reviewed-by: Vijay Bellur <vbellur> Tested-by: Gluster Build System <jenkins.com> REVIEW: http://review.gluster.org/5971 (glusterd: Don't reset rebalance status on add-brick) posted (#1) for review on release-3.4 by Kaushal M (kaushal) COMMIT: http://review.gluster.org/5971 committed in release-3.4 by Anand Avati (avati) ------ commit ac92dccc8727acaa3c9e9353fba80817947552bf Author: Kaushal M <kaushal> Date: Tue Sep 10 15:33:00 2013 +0530 glusterd: Don't reset rebalance status on add-brick Backport of 67c28b19355c47e96d1420405cc38753a3e5f9be from master The rebalance status was being reset to 'Not started' when add-brick was performed. This would lead to odd cases where a 'rebalance status' on a volume would show status as 'not started' but would also include the rebalance statistics. This also affected the showing of asynchronus task status in 'volume status' command. By not resetting the status prevent the above issues from happening. Since we use the running/not-running of the rebalance process as the check when performing other operations we can safely leave the rebalance stats collected on an add-brick. BUG: 1006247 Change-Id: Idade88d9e5a6f27659490b3e6d85495d426ef0a3 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/5971 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |