Von: knarra [mailto:knarra(a)redhat.com]
Gesendet: Montag, 24. April 2017 13:44
An: Sven Achtelik <Sven.Achtelik(a)eps.aero><= /a>; users(a)ovirt.org
Betreff: Re: [ovirt-users] Hyperconverged Setup and Gluster healing

=C2=A0

On 04/24/2017 05:03 PM, Sven Achtelik wrote:=

Hi All,

=C2=A0

my oVirt-Setup is 3 Hosts with gluster and reaplica 3. I always try to stay on the current version and I=C2=92m applying updates/upgrade if there are any. For this I put a host in maintenance and also use the =C2=93Stop Gluster Service=C2=94 =C2=A0checkbox.= After it=C2=92s done updating I=C2=92ll set it back to active and wait until the engine sees all bricks again and then I=C2=92ll go for the next host.

=C2=A0

This worked fine for me the last month and now that I have more and more VMs running the changes that are written to the gluster volume while a host is in maintenance become a lot more and it takes pretty long for the healing to complete. What I don=C2=92t understand is that I don=C2=92t really see a lot of network usage in the GUI during that time and it feels quiet slow. The Network for the gluster is a 10G and I=C2=92m quiet happy with the performance of it, it=C2=92s just the healing that takes long. I noticed that because I couldn=C2= =92t update the third host because of unsynced gluster volumes.

=C2=A0

Is there any limiting variable that slows down traffic during healing that needs to be configured ? Or should I maybe change my updating process somehow to avoid having so many changes in queue?

=C2=A0

Thank you,

=C2=A0

Sven

=C2=A0
_______________________________________________
          Users mailing list
          Users(a)ovirt.org
          http://lists.ovirt.org/mailman/listinfo/users
        

Hi Sven,

=C2=A0=C2=A0=C2=A0 Do you have granular entry heal enabled on th= e volume? If no, there is a feature called granular entry self-heal which should be enabled with sharded volumes to get the benefits. So when a brick goes down and say only 1 in those million entries is created/deleted. Self-heal would be done for only that file it won't crawl the entire directory.

=C2=A0=C2=A0=C2=A0 You can run=C2=A0glu= ster volume set=C2=A0VOLNAME= =C2=A0clu= ster.granular-entry-heal enable / disable=C2=A0command only if the volume is in=C2=A0= Cre= ated=C2=A0state. If the volume is in any other state other than=C2=A0Cre= ated=C2=A0, for example,=C2=A0Sta= rted=C2=A0,=C2=A0Sto= pped, and so on, execute=C2=A0glu= ster volume heal VOLNAME granular-entry-heal=C2=A0enable / disable=C2=A0= command to enable or disable granular-entry-heal option.

Thanks

kasturi