Hi Kevin,
are you using Proxmox, right ?
I think it's important because Proxmox uses gfapi to connect each VM to
the disk, not FUSE. Maybe this is important to find the cause.
I had a similar issue while moving machines from an old gluster volume
to a new volume with sharding enabled and I added new bricks to it.
Xavi
On 17/10/16 08:46, Kevin Lemonnier wrote:
I see that network.ping-timeout on your setup is 15 seconds andA that's
too low. Could you reconfigure that to 30 seconds?
Yes, I can. I set it to 15 to be sure no browser would timeout when trying to load
a website on a frozen VM during the timeout, 15 seemed pretty good since it just
feels like the website was a bit slow, which happens. I guess 30 should still work,
do you think 15 could cause problems ? We've had that on our clusters for a few months
already without noticing anything. The heals are totally transparent now so I figured
I don't really mind if it heals everytime there is a little lag ..
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
