Bug 1380598
| Summary: | RFE: An administrator friendly way to determine rebalance completion time | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Alok <asrivast> | |
| Component: | distribute | Assignee: | Nithya Balachandran <nbalacha> | |
| Status: | CLOSED ERRATA | QA Contact: | Prasad Desala <tdesala> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.2 | CC: | amukherj, bkunal, dkanemat, mchangir, mpillai, nbalacha, rhinduja, rhs-bugs, storage-qa-internal, tsugano | |
| Target Milestone: | --- | Keywords: | FutureFeature | |
| Target Release: | RHGS 3.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-24 | Doc Type: | Enhancement | |
| Doc Text: |
The 'gluster volume $volname rebalance status' command now provides an estimate of the time left to rebalance completion. Note that calculations are based on each brick having its own file system partition, and will be more accurate the larger the data set.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1396004 1436681 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-21 04:28:23 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: | 1396004, 1415915 | |||
| Bug Blocks: | 1369781, 1417138, 1417145, 1436681 | |||
|
Description
Alok
2016-09-30 04:42:20 UTC
upstream patch : http://review.gluster.org/15893 downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101294/ @Nithya - As per our discussion, I guess you'd also want to enhance this feature by a bit more. I'm not moving this bug to MODIFIED till I hear from you. Tested this BZ against glusterfs version 3.8.4-23.el7.x86_64. When triggered add-brick rebalance or remove-brick, "gluster vol vol-name rebalance status" is not displaying the approximate time to complete the rebalance. Moving this BZ to Assigned state. Issue has been RCAed and it was due to git merge behaving oddly or probably a manual mistake of resolving merge conflicts. A piece of code where volinfo.rebal.time_left was populated with the calculated time left was missed out and hence in cli parsing it was always coming as zero and as per the logic if the estimated rebalance time left is 0 nothing additional is shown up. https://code.engineering.redhat.com/gerrit/104300 Verified this BZ on glusterfs version 3.8.4-24.el7rhgs.x86_64. Now, we are seeing rebalance estimated time during add-brick rebalance and remove-brick operation. Tested with a file count of 70k for which add-brick rebalance and remove-brick took appx 18 minutes to complete, I observed that the rebalance estimated time it is showing is very inaccurate like as mentioned in Comment 8. As the very basic add-brick and remove-brick two cases are displaying the rebalance est time, I am moving this BZ to Verified state. Will open a new BZ if seen any issues wrt rebalance estimation time during functional testing. Hi Laura, Can you also please add that estimates are expected to be more accurate for larger data sets? Thanks, Nithya Thanks Laura. The text looks good. 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-2017:2774 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-2017:2774 |