Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1704252

Summary: Creation of bulkvoldict thread logic is not correct while brick_mux is enabled for single volume
Product: [Community] GlusterFS Reporter: Mohit Agrawal <moagrawa>
Component: glusterdAssignee: Mohit Agrawal <moagrawa>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1704769 (view as bug list) Environment:
Last Closed: 2019-04-30 13:11:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1704769    

Description Mohit Agrawal 2019-04-29 12:32:43 UTC 
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:
Comment 1 Worker Ant 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