+++ This bug was initially created as a clone of Bug #1689799 +++ Description of problem: When we use heal info command it takes lot of time as some cases it takes lock on entries to find out if the entry actualy needs heal or not. There are some cases where we can avoid these locks and can conclude if the entry needs heal or not. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Worker Ant on 2019-03-18 08:27:59 UTC --- REVIEW: https://review.gluster.org/22372 (cluster/ec: Fix handling of heal info cases without locks) posted (#1) for review on master by Ashish Pandey --- Additional comment from Worker Ant on 2019-04-04 21:06:32 UTC --- REVIEW: https://review.gluster.org/22372 (cluster/ec: Fix handling of heal info cases without locks) merged (#5) on master by Xavi Hernandez
REVIEW: https://review.gluster.org/22532 (cluster/ec: Fix handling of heal info cases without locks) posted (#2) for review on release-6 by Ashish Pandey
REVIEW: https://review.gluster.org/22532 (cluster/ec: Fix handling of heal info cases without locks) merged (#2) on release-6 by Ashish Pandey
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.1, please open a new bug report. glusterfs-6.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-April/000124.html [2] https://www.gluster.org/pipermail/gluster-users/