Bug 1704769

Summary:	Creation of bulkvoldict thread logic is not correct while brick_mux is enabled for single volume
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohit Agrawal <moagrawa>
Component:	glusterd	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Kshithij Iyer <kiyer>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.5	CC:	amukherj, nchilaka, rhinduja, rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1704252	Environment:
Last Closed:	2019-10-30 12:20:55 UTC	Type:	---
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:	1704252
Bug Blocks:	1696807

Description Mohit Agrawal 2019-04-30 13:13:54 UTC

+++ 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

Comment 2 Mohit Agrawal 2019-04-30 13:17:26 UTC

The patch is already merged in upstream
https://review.gluster.org/22647

Comment 11 errata-xmlrpc 2019-10-30 12:20:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:3249