[Bugs] [Bug 1684404] New: Multiple shd processes are running on brick_mux environmet

bugzilla at redhat.com bugzilla at redhat.com
Fri Mar 1 08:00:34 UTC 2019


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

            Bug ID: 1684404
           Summary: Multiple shd processes are running on brick_mux
                    environmet
           Product: GlusterFS
           Version: mainline
          Hardware: x86_64
            Status: NEW
         Component: glusterd
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: mchangir at redhat.com
                CC: bugs at gluster.org, moagrawa at redhat.com, pasik at iki.fi
        Depends On: 1683880
            Blocks: 1672818 (glusterfs-6.0)
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1683880 +++

Description of problem:
Multiple shd processes are running while created 100 volumes in brick_mux
environment

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


How reproducible:
Always

Steps to Reproduce:
1. Create a 1x3 volume 
2. Enable brick_mux
3.Run below command
n1=<ip>
n2=<ip>
n3=<ip>

for i in {1..10};do
    for h in {1..20};do
                gluster v create vol-$i-$h rep 3
$n1:/home/dist/brick$h/vol-$i-$h $n2:/home/dist/brick$h/vol-$i-$h
$n3:/home/dist/brick$h/vol-$i-$h force
                gluster v start vol-$i-$h
                sleep 1
     done
done
for k in $(gluster v list|grep -v heketi);do gluster v stop $k
--mode=script;sleep 2;gluster v delete $k --mode=script;sleep 2;done

Actual results:
Multiple shd processes are running and consuming system resources

Expected results:
Only one shd process should be run

Additional info:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1672818
[Bug 1672818] GlusterFS 6.0 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1683880
[Bug 1683880] Multiple shd processes are running on brick_mux environmet
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list