[Bugs] [Bug 1438370] rebalance: Allow admin to change thread count for rebalance
bugzilla at redhat.com
bugzilla at redhat.com
Sat Apr 29 14:29:38 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1438370
--- Comment #6 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16980 committed in master by Raghavendra G
(rgowdapp at redhat.com)
------
commit d51288540241d1f7785bb17bdc0702c0879087a9
Author: Susant Palai <spalai at redhat.com>
Date: Wed Mar 22 17:14:25 2017 +0530
cluster/dht: Make rebalance throttle option tuned by number
Current rebalance throttle options: lazy/normal/aggressive may not always
be
sufficient for the purpose of throttling. In our recent test, we observed
for
certain setups, normal and aggressive modes behaved similarly consuming
full
disk bandwidth. So in cases like this admin should be able to tune it
down(or vice versa) depending on the need.
Along with old throttle configurations, thread counts are tuned based on
number.
e.g. gluster v set vol-name cluster-rebal.throttle 5.
Admin can tune up/down between 0 and the number of cores available.
Note: For heterogenous servers, validation will fail on the old server if
"number"
is given for throttle configuration.
The message looks something like this:
"volume set: failed: Staging failed on vm2. Error: cluster.rebal-throttle
should be {lazy|normal|aggressive}"
Test: Manual test by logging active thread number after reconfiguring
throttle option.
testcase: tests/basic/distribute/throttle-rebal.t
Change-Id: I46e3cde546900307831028b344ecf601fd9b02c3
BUG: 1438370
Signed-off-by: Susant Palai <spalai at redhat.com>
Reviewed-on: https://review.gluster.org/16980
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Smoke: Gluster Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
--
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=G6CNPOnhDB&a=cc_unsubscribe
More information about the Bugs
mailing list