[Bugs] [Bug 1656951] cluster.max-bricks-per-process 250 not working as expected

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1656951



--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
Description of problem:
On a 3 node gluster cluster with 1000+ volumes `pidof glusterfsd` returns only
one single pid instead of returning 4 pids even when the default value of
cluster.max-bricks-per-process is set to 250.

# gluster v get all all
Option                                  Value                                  
------                                  -----                                  
cluster.server-quorum-ratio             51                                     
cluster.enable-shared-storage           disable                                
cluster.op-version                      31304                                  
cluster.max-op-version                  31304                                  
cluster.brick-multiplex                 enable                                 
cluster.max-bricks-per-process          250                                    
cluster.daemon-log-level                INFO                        

# pidof glusterfsd
31746

Version-Release number of selected component (if applicable):
glusterfs-3.12.2-31

How reproducible:
1/1

Steps to Reproduce:
1.Set cluster.brick-multiplex to enable.
# gluster v get all all
Option                                  Value                                  
------                                  -----                                  
cluster.server-quorum-ratio             51                                     
cluster.enable-shared-storage           disable                                
cluster.op-version                      31304                                  
cluster.max-op-version                  31304                                  
cluster.brick-multiplex                 enable                                 
cluster.max-bricks-per-process          250                                    
cluster.daemon-log-level                INFO                                

2.Create 1000+ volumes of type replica 1x3.
3.Execute `pidof glusterfsd` command on any node.(It'll return only a single
pid)
# pidof glusterfsd
31746

Actual results:
`pidof glusterfsd` returns only a single pid. (Observed across all nodes.)
# pidof glusterfsd
31746

Expected results:
`pidof glusterfsd` should return 4 pids which means each process will have 250
volumes attached to it.
# pidof glusterfsd
31746 <xxxxx> <xxxxx> <xxxxx>

Additional info:
Even after stopping and starting all volumes `pidof glusterfsd` was returning
only one pid instead of returning four pids.



Root Cause:

In get_mux_limit_per_process (), glusterd looks for the
cluster.max-bricks-per-process value from the global option dictionary but
never falls back to the default from the global option table in case the global
option dictionary doesn't have it which is usual until and unless the option is
not reconfigured.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.