+++ 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
The patch is already merged in upstream https://review.gluster.org/22647
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