Hide Forgot
if we change the multithreaded self heal options to utilize this feature, the user needs to restart the self heal deamon, otherwise the healing will still be single threaded. We need to document this. Restart of selfheal deamon can be done by volume start force [root@dhcp35-179 ~]# rpm -qa|grep gluster glusterfs-libs-3.8.4-3.el7rhgs.x86_64 glusterfs-cli-3.8.4-3.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-3.el7rhgs.x86_64 glusterfs-server-3.8.4-3.el7rhgs.x86_64 glusterfs-debuginfo-3.8.4-2.26.git0a405a4.el7rhgs.x86_64 glusterfs-fuse-3.8.4-3.el7rhgs.x86_64 glusterfs-api-3.8.4-3.el7rhgs.x86_64 glusterfs-3.8.4-3.el7rhgs.x86_64 [root@dhcp35-179 ~]# this problem exists for both AFR and EC volumes Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information:
Alok, According to the bug description, we must restart selfheal daemon using volume start force command to start multithreaded self-heal. In the RHGS Administration Guide, we have not documented "volume start force" command. Not sure if start force is recommended in the production environment. Hence, wanted a confirmation from you before I document "volume start force" option in the Admin Guide? Thanks!
MT self-heal existed in the previous release for AFR . What was the behavior in 3.1.3 ?
It has been the same for even previous release. We need to restart even then, only the self heal deamon(use vol start force)
Alok. Nag Pavan has clarified that the behavior was same in 3.1.3 as well. Could you please share your thoughts on how can we address this issue? Thanks!