I would advise you to experiment with incrementing the background self heal count a little at a time till you achieve optimal performance. Unfortunately I can't give you hard numbers because this kind of tuning is more of an art than a science because of the number of possible variables which come into play depending on your hardware configuration and exact use case.
-- Sent from my HP Pre3
On Sep 5, 2014 4:16 AM, justglusterfs@xxxxxxxxx <justglusterfs@xxxxxxxxx> wrote:
Hi all：
I do the following test：
I create a glusterfs replica volume (replica count is 2 ) with two server node(server A and server B)， then mount the volume in client node，
then， I shut down the network of server A node， in client node， I copy a dir（which has a lot of small files）， the dir size is 2.9GByte，
when copy finish， I start the network of server A node， now， glusterfs self-heal-daemon start heal dir from server B to server A，
in the end， I find the self-heal-daemon heal the dir use 40 minutes， It's too slow！ why？
I find out related options with self-heal， as follow：
cluster.self-heal-window-size
cluster.self-heal-readdir-size
cluster.background-self-heal-count I want to ask， modify the above options can improve the performance of heal dir？ if possible， please give a reasonable value about above options。
thanks！
justglusterfs@xxxxxxxxx
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
