+++ This bug was initially created as a clone of Bug #1711249 +++ Description of problem: In commit ac70f66c5805e10b3a1072bd467918730c0aeeb4 one condition was missed to handle volumes by bulkvoldict thread so at the time of getting friend request from peer, glusterd is not sending all volumes updates to peers. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Setup 500 volumes(test1..test500 1x3) 2. Enable brick_multiplex 3. Stop glusterd on one node 4. Update "performance.readdir-ahead on" for volumes periodically like test1,test20,test40,test60,test80...test500 5. Start glusterd on 6. Wait 2 minutes to finish handshake and then check the value of performance.readdir-ahead for volumes (test1,test20,test40,....test500) The value should be sync by peer nodes Actual results: For some of the volumes value is not synced. Expected results: For all the volumes value should be synced Additional info: --- Additional comment from RHEL Product and Program Management on 2019-05-17 11:17:45 UTC --- This bug is automatically being proposed for the next minor release of Red Hat Gluster Storage by setting the release flag 'rhgs‑3.5.0' to '?'. If this bug should be proposed for a different release, please manually change the proposed release flag.
REVIEW: https://review.gluster.org/22739 (glusterd: bulkvoldict thread is not handling all volumes) posted (#1) for review on master by MOHIT AGRAWAL
REVIEW: https://review.gluster.org/22739 (glusterd: bulkvoldict thread is not handling all volumes) merged (#2) on master by Atin Mukherjee