Bug 1474342 - reset cluster.max-bricks-per-process value when brick mux is disabled
reset cluster.max-bricks-per-process value when brick mux is disabled
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Atin Mukherjee
Bala Konda Reddy M
Depends On:
  Show dependency treegraph
Reported: 2017-07-24 08:30 EDT by nchilaka
Modified: 2017-07-25 06:15 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-25 06:15:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description nchilaka 2017-07-24 08:30:17 EDT
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):

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.