<p dir="ltr">Il 01 giu 2016 22:34, "Gmail" <<a href="mailto:b.s.mikhael@gmail.com">b.s.mikhael@gmail.com</a>> ha scritto:<br>
><br>
><br>
>> On Jun 1, 2016, at 1:25 PM, Gandalf Corvotempesta <<a href="mailto:gandalf.corvotempesta@gmail.com">gandalf.corvotempesta@gmail.com</a>> wrote:<br>
>> with nfs replication is made directly by gluster servers with no client involved?<br>
><br>
> correct</p>
<p dir="ltr">This is good<br>
what i really don't like in gluster is the client doing all the replication.<br>
replication and cluster management should be done directly by servers, not by clients<br>
client side the resources used for replication and cluster management could be used for something else like virtualizations and so on.</p>
<p dir="ltr">> the NFS client talks to only one NFS server (the one which it mounts), the NFS HA setup is only to failover a virtual IP to another healthy node. so the NFS client will just do 3 minor timeouts then it will do a major timeout, when that happens, the virtual IP failover will be already done.<br></p>
<p dir="ltr">The same is for native client.<br>
even the native client has to wait for a timeout before changing the storage node, right?<br>
what happens to a virtual machine writing to disk during this timeout? <br>
</p>