[Bugs] [Bug 1472417] No clear method to multiplex all bricks to one process( glusterfsd) with cluster.max-bricks-per-process option

bugzilla at redhat.com bugzilla at redhat.com
Wed Jul 19 20:17:31 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1472417



--- Comment #5 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17819 committed in master by Jeff Darcy
(jeff at pl.atyp.us) 
------
commit acdbdaeba222e9ffeae077485681e5101c48d107
Author: Samikshan Bairagya <samikshan at gmail.com>
Date:   Tue Jul 18 21:33:45 2017 +0530

    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 at gmail.com>
    Reviewed-on: https://review.gluster.org/17819
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

-- 
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=bh41t4Viv6&a=cc_unsubscribe


More information about the Bugs mailing list