Hi Kasturi,

I’= ll try=3D that. Will this be persistent over a reboot of a host or even stopping of = =3D the complete cluster ?

<= o:p>&n=3D bsp;

Thank you

<=3D p class=3D3DMsoNormal>Von: knarra [mailto:knarra(a)redhat.com]
Gesendet: Montag, 24. Apr= il=3D 2017 13:44
An: Sven Achtelik <Sven.Achtelik(a)eps.aero>; u= se=3D rs(a)ovirt.org
Betreff: Re: [ovirt-users] Hyperconverged Setup an= d =3D Gluster healing

=3D

On 04/24/2017 05:03 PM, Sven Ac= ht=3D elik wrote:=

Hi All,
&= nbsp=3D ;
my oVirt-Setup = is 3=3D Hosts with gluster and reaplica 3. I always try to stay on the current ver= =3D sion and I’m applying updates/upgrade if there are any. For this I pu= =3D t a host in maintenance and also use the “Stop Gluster Service”= =3D checkbox. After it’s done updating I’ll set it back to a= =3D ctive and wait until the engine sees all bricks again and then I’ll g= =3D o for the next host.

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

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

=3D Thank you,

Sven
<=3D /p>
__________________________________________=
=3D
_____
Users mailing list
Users(a)ovirt.org
=
http://lists.ovirt.or=
g/=3D
mailman/listinfo/users

Hi Sven,

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

You can run <=3D code>glus= te=3D r volume set VOLNAME cluster.granular-e= nt=3D ry-heal enable / disable<=3D span style=3D3D'font-size:11.0pt;font-family:"Courier New";color:#333333;ba= ck=3D ground:white'> command only if the volume is in&=3D nbsp;Created state. If the volume is in any other state other than Created , for example,&n= bs=3D p;Started =3D , Stopped<=3D span style=3D3D'color:#333333;background:white'>, and so on, execute gluster volume heal VOLNAME granu= =3D lar-entry-heal enable / disable command to enable or disable granular-entry-= =3D heal option.

Thanks

kasturi