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 <[email protected]> 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
>[email protected]
>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
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
