glusterfs

History

Samikshan Bairagya acdbdaeba2 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>

2017-07-19 20:17:27 +00:00

cluster

libglusterfs: Name threads on creation

2017-07-19 14:16:19 +00:00

debug

libglusterfs: Name threads on creation

2017-07-19 14:16:19 +00:00

encryption

coreutils: use coreutils instead of duplicate code

2017-05-05 15:04:17 +00:00

experimental

libglusterfs: Name threads on creation

2017-07-19 14:16:19 +00:00

features

libglusterfs: Name threads on creation

2017-07-19 14:16:19 +00:00

lib/src

quota: add version to quota xattrs

2015-11-02 00:54:35 -08:00