Bug 1474342 - reset cluster.max-bricks-per-process value when brick mux is disabled
Summary: reset cluster.max-bricks-per-process value when brick mux is disabled
Keywords:
Status: CLOSED NOTABUG
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:30 UTC by Nag Pavan Chilakam
Modified: 2017-08-31 13:46 UTC (History)
5 users (show)

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

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.