Hi. this has been glusters approach from the beginning.. if you read the wiki, > there are recommendations for how to force auto-healing. look for some find > commands what will do what you want. > > While, form a raw high-availability approach, the on-access healing doesn't > really help when faced with potential of multiple failures, from a > performance approach it's ideal. > otherwise, each AFR server has to retain a transaction log. This would > likely have to be stuck on the underlying filesystem, as some weird file or > something, or just consume vast amounts of memory. > > so while it may not be ideal in your circumstance, knowing how it behaves > and knowing how to force auto-healing should make it work well for you. > So, basically the recommended approach is to run "find" every time a server goes down or comes up? How then one insures files are re-balanced on remaining servers? I mean, AFR would just look for the next free server and it put them there? And after the problematic server comes up again, AFR would erase the redundant file copies from it? Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081207/1a58b32d/attachment.htm
