Re: NFS or Lustre like behavior when client/server becomes unreachable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



One option would be to use a replicated volume. Then your clients would be able to continue operation in the event of a server loss.

On May 1, 2014 2:08:05 AM MDT, Franco Broi <franco.broi@xxxxxxxxxx> 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@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux