Hi Danson, Updating the replica only on the next access is not the best solution for the reasons mentioned by you. We will announce the AFR's auto-sync design to the list soon. It is scheduled for 1.4.
Regards Krishna On 5/12/07, Danson Michael Joseph <[EMAIL PROTECTED]> wrote:
Hi Again, I just read that the CODA filesystem can replicate to multiple servers, and when a server goes down and comes back up some time after files on the remaining server have changed, the policy for repair is to repair on next access. Now I don't believe that this policy is ideal because if the second server then fails before a file has been accessed, the file is not up to date, but it does highlight a possible repair technique whereby the client does a loopback write for all files with different timestamps or some other marked difference? Regards, Danson _______________________________________________ Gluster-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gluster-devel
