[Gluster-users] NFS or Lustre like behavior when client/server becomes unreachable

[Justin Dossey]

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 at iongeo.com> wrote:

> On Wed, 2014-04-30 at 21:29 +0200, Michal Pazdera wrote:
> > 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.
>
> This is what we would like too.
>
> 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 at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>



-- 
Justin Dossey
CTO, PodOmatic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140502/8d0ff127/attachment.html>