Bug 1474344

Summary:	Allow only the maximum number of bricks supported for cluster.max-bricks-per-process
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nag Pavan Chilakam <nchilaka>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CANTFIX	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	brick-multiplexing
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-26 13:15:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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: