summaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
authorSamikshan Bairagya <samikshan@gmail.com>2017-07-18 21:33:45 +0530
committerJeff Darcy <jeff@pl.atyp.us>2017-07-19 20:17:27 +0000
commitacdbdaeba222e9ffeae077485681e5101c48d107 (patch)
treefdc658eb331a589d3f177b6468593d31e670b9f7 /tests
parent33db9aff1deaa028f30516e49fdb1e8d6e31bb73 (diff)
glusterd: Set default value for cluster.max-bricks-per-process to 0
When brick-multiplexing is enabled, and "cluster.max-bricks-per-process" isn't explicitly set, multiplexing happens without any limit set. But the default value set for that tunable is 1, which is confusing. This commit sets the default value to 0, and prevents the user from being able to set this value to 1 when brick-multiplexing is enbaled. The default value of 0 denotes that brick-multiplexing can happen without any limit on the number of bricks per process. Change-Id: I4647f7bf5837d520075dc5c19a6e75bc1bba258b BUG: 1472417 Signed-off-by: Samikshan Bairagya <samikshan@gmail.com> Reviewed-on: https://review.gluster.org/17819 Smoke: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Atin Mukherjee <amukherj@redhat.com> CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Diffstat (limited to 'tests')
-rw-r--r--tests/basic/mpx-compat.t1
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/basic/mpx-compat.t b/tests/basic/mpx-compat.t
index 3de0f6fe7cb..4ca262ee349 100644
--- a/tests/basic/mpx-compat.t
+++ b/tests/basic/mpx-compat.t
@@ -15,6 +15,7 @@ function count_processes {
pgrep glusterfsd | wc -w
}
+cleanup
TEST glusterd
TEST $CLI volume set all cluster.brick-multiplex yes
push_trapfunc "$CLI volume set all cluster.brick-multiplex off"