I just checked the code. All `statistics heal-count` does is to count the number of indices (in other words the number of files to be healed) present per brick in the .glusterfs/indices/xattrop directory - which is where we hold empty files representing inodes that need heal - and prints them. I even tested it on my local setup, in terms of creating a few thousand files and writing data into them while a brick is down and then executing the command after bringing the brick back up periodically. It worked for me.
`heal info` also reads individual indices in the same directory, but it takes locks to confirm they need heal by examining the pending xattrs. Could you describe how you ran into this issue? -Krutika On Fri, Apr 15, 2016 at 6:22 PM, Lindsay Mathieson < [email protected]> wrote: > Currently on my cluster: > > > "gluster volume heal <DS> statistic heal-count" shows zero to heal on > all nodos > > but > > "gluster volume heal <DS> info" > > shows multiple shards on all nodes, and it keeps updating. > > > -- > Lindsay Mathieson > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
