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: