Bug 1474344 - Allow only the maximum number of bricks supported for cluster.max-bricks-per-process
Summary: Allow only the maximum number of bricks supported for cluster.max-bricks-per...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Atin Mukherjee
QA Contact: Bala Konda Reddy M
URL:
Whiteboard: brick-multiplexing
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 12:34 UTC by Nag Pavan Chilakam
Modified: 2017-08-31 13:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-26 13:15:22 UTC
Embargoed:

Attachments (Terms of Use)

Description Nag Pavan Chilakam 2017-07-24 12:34:15 UTC 
Description of problem:
======================
Note: this is a cosmetic bug and no functional impact
for cluster.max-bricks-per-process , we can set any unsigned integer.
that means we can set even a value like 1000000000000000
However, from what I recollect the max number of bricks less than 100(kindly confirm, as i couldn't find the right doc at the moment)

So we the range of cluster.max-bricks-per-process should be b/w 0 to max number of bricks we support

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




Additional info:
Note You need to log in before you can comment on or make changes to this bug.