On 04/14/2016 09:46 AM, Lindsay Mathieson wrote:> Sorry to bring this up again, but I never did figure out the right > settings for this. > > If I reboot a gluster node for a rep 3 volume, what are the settings > for maximising heal speed, assuming ones not worried about i/o or cpu > > Gluster 3.7.9 > Sharded volume (4MB)The only benefit you get over replicate volumes without sharding is that only the shards which changed when the brick rebooted are healed instead of whole VM image. Apart from that I don't see any settings that will improve heal speed. You wait for 3.7.12. We are almost done backporting multi-threaded self-heal. I am in the process of writing a blog-post to give full idea about this one. Pranith> > thanks, >
Hi, Just curious, are you seeing poor heal performance of VMs by any chance in 3.7.9 *even* with sharding? -Krutika On Thu, Apr 14, 2016 at 3:14 PM, Pranith Kumar Karampuri < pkarampu at redhat.com> wrote:> > > On 04/14/2016 09:46 AM, Lindsay Mathieson wrote: > >> Sorry to bring this up again, but I never did figure out the right >> settings for this. >> >> If I reboot a gluster node for a rep 3 volume, what are the settings >> for maximising heal speed, assuming ones not worried about i/o or cpu >> >> Gluster 3.7.9 >> Sharded volume (4MB) >> > The only benefit you get over replicate volumes without sharding is that > only the shards which changed when the brick rebooted are healed instead of > whole VM image. Apart from that I don't see any settings that will improve > heal speed. You wait for 3.7.12. We are almost done backporting > multi-threaded self-heal. I am in the process of writing a blog-post to > give full idea about this one. > > Pranith > >> >> thanks, >> >> > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160414/7ea5d783/attachment.html>
>>>We are almost done backporting multi-threaded self-heal. I am in the process of writing a blog-post to give full idea about this one.Will multi thread self heal work for disperse volumes? what is the blog address? On Thu, Apr 14, 2016 at 12:44 PM, Pranith Kumar Karampuri <pkarampu at redhat.com> wrote:> > > On 04/14/2016 09:46 AM, Lindsay Mathieson wrote: >> >> Sorry to bring this up again, but I never did figure out the right >> settings for this. >> >> If I reboot a gluster node for a rep 3 volume, what are the settings >> for maximising heal speed, assuming ones not worried about i/o or cpu >> >> Gluster 3.7.9 >> Sharded volume (4MB) > > The only benefit you get over replicate volumes without sharding is that > only the shards which changed when the brick rebooted are healed instead of > whole VM image. Apart from that I don't see any settings that will improve > heal speed. You wait for 3.7.12. We are almost done backporting > multi-threaded self-heal. I am in the process of writing a blog-post to give > full idea about this one. > > Pranith >> >> >> thanks, >> > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users
On 14/04/2016 7:44 PM, Pranith Kumar Karampuri wrote:> The only benefit you get over replicate volumes without sharding is > that only the shards which changed when the brick rebooted are healed > instead of whole VM image. Apart from that I don't see any settings > that will improve heal speed. You wait for 3.7.12. We are almost done > backporting multi-threaded self-heal. I am in the process of writing a > blog-post to give full idea about this one.Awesome, I look fwd to it Pranith. BTW, quite happy with the exiting heal, its fast enough and has minimal impact on the cluster. I'd just like to max it out once in a while ;) -- Lindsay Mathieson