Any reason you can't just set network.ping-timeout to a very large number?
On Thu, May 1, 2014 at 1:08 AM, Franco Broi <franco.broi@xxxxxxxxxx> wrote:
On Wed, 2014-04-30 at 21:29 +0200, Michal Pazdera wrote:This is what we would like too.
> What we would like to achieve is the same behavior as NFS or Lustre
> does
> where running client jobs hang until
> the target is back online and then continues in the job.
I think it's reasonable for a job that is in the process of writing a
file on a brick that disappears to fail but interrupted reads should be
recoverable.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
Justin Dossey
CTO, PodOmatic
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
