If I understand the query correctly, the problem is that gluster takes
more than 20seconds to timeout even though the brick was offline for
more than 35s. With that assumptions I have some
How did you understand that the timer has expired after 35s only, by log
file? If so glusterfs wait some
Hello Gluster Community
We have 2x brick nodes running with replication for a volume gv0 for which set a
"gluster volume set gv0 ping-timeout 20".
In our tests it seemed there is unknown delay with this ping-timeout - we see it
timing out much later after about 35 seconds and not at around 20
