Bug 1474342

Summary:	reset cluster.max-bricks-per-process value when brick mux is disabled
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nag Pavan Chilakam <nchilaka>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED NOTABUG	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	amukherj, nchilaka, 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-25 10:15:31 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:30:17 UTC

Description of problem:
Note:this is a cosmentic bug and no functionality is impacted, hence raising as low severity
when brick mux is enabled and user sets some value to cluster.max-bricks-per-process, say 20
and later disables brick mux, then we must be reseting the value of cluster.max-bricks-per-process to 1( not even 0, as 1 makes more sense)

However, we still keep the value as 20 with brick mux now disabled



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

How reproducible:


Steps to Reproduce:
1.enable brick mux and set cluster.max-bricks-per-process  to 20
2. now disable brick mux 


Actual results:
===============
brick mux disablement must set cluster.max-bricks-per-process  to 1  or 0