[Bugs] [Bug 1653073] New: default cluster.max-bricks-per-process to 250

bugzilla at redhat.com bugzilla at redhat.com
Sun Nov 25 14:35:45 UTC 2018


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

            Bug ID: 1653073
           Summary: default cluster.max-bricks-per-process to 250
           Product: Red Hat Gluster Storage
         Component: glusterd
          Assignee: amukherj at redhat.com
          Reporter: amukherj at redhat.com
        QA Contact: bmekala at redhat.com
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    sankarshan at redhat.com, storage-qa-internal at redhat.com,
                    vbellur at redhat.com
        Depends On: 1652118
   External Bug ID: Gluster.org Gerrit 21701



+++ This bug was initially created as a clone of Bug #1652118 +++

Description of problem:

In a scale container storage setup which hosts ~1000 1 X 3 volumes, its seen
that if a single brick process is going to host all the rest of 999 brick
instances, the overall footprint of the brick process might still be at the
higher side. We already have an option cluster.max-bricks-per-process which
when set to a value n, that's the max cap of number of brick instances to be
attached to a brick process. We have seen benefits in defining a cap of 250 of
bricks per process in few scale deployments where things haven't gone crazy
like glusterd taking lots of time to process disconnect events, bricks not
reaching to a warning level of OOM killer situation etc.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2018-11-21 10:50:14 EST ---

REVIEW: https://review.gluster.org/21701 (glusterd: make max-bricks-per-process
default value to 250) posted (#1) for review on master by Atin Mukherjee

--- Additional comment from Worker Ant on 2018-11-25 09:34:31 EST ---

REVIEW: https://review.gluster.org/21701 (glusterd: make max-bricks-per-process
default value to 250) posted (#2) for review on master by Atin Mukherjee


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1652118
[Bug 1652118] default cluster.max-bricks-per-process to 250
-- 
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=QYiIZ49hVR&a=cc_unsubscribe


More information about the Bugs mailing list