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

bugzilla at redhat.com bugzilla at redhat.com
Wed Nov 21 15:48:16 UTC 2018


            Bug ID: 1652118
           Summary: default cluster.max-bricks-per-process to 250
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org

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:

Actual results:

Expected results:

Additional info:

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list