[Bugs] [Bug 1704769] New: Creation of bulkvoldict thread logic is not correct while brick_mux is enabled for single volume

[bugzilla at redhat.com]

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

            Bug ID: 1704769
           Summary: Creation of bulkvoldict thread logic is not correct
                    while brick_mux is enabled for single volume
           Product: Red Hat Gluster Storage
           Version: rhgs-3.5
            Status: NEW
         Component: glusterd
          Assignee: amukherj at redhat.com
          Reporter: moagrawa at redhat.com
        QA Contact: bmekala at redhat.com
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    sankarshan at redhat.com, storage-qa-internal at redhat.com,
                    vbellur at redhat.com
        Depends On: 1704252
  Target Milestone: ---
    Classification: Red Hat



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

Description of problem:
Ideally, glusterd should spawn bulvoldict thread only while no. of volumes are
high more than 100 and brick_mux is enabled.

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


How reproducible:
Always

Steps to Reproduce:
1.Setup 1x3 cluster environment and enable brick_mux
2.Stop/start glusterd on one node
3. Check the messages in glusterd.log, it is showing below logs
  Create thread 1 to populate dict data for volume start index is 1 end index 
  is 2
[[glusterd-utils.c:3559:glusterd_add_volumes_to_export_dict] 0-management:
Finished dictionary popluation in all threads

Actual results:
dict thread is creating even no. of volume is 1

Expected results:
No need to create dict thread if volume count is lower

Additional info:

--- Additional comment from Worker Ant on 2019-04-30 13:11:17 UTC ---

REVIEW: https://review.gluster.org/22647 (glusterd: Fix bulkvoldict thread
logic in brick multiplexing) merged (#6) on master by Atin Mukherjee


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1704252
[Bug 1704252] Creation of bulkvoldict thread logic is not correct while
brick_mux is enabled for single volume
-- 
You are receiving this mail because:
You are on the CC list for the bug.