Two solutions:
1) use locking when doing write() (applications responsibility)
2) load afr on server side so that afr is a single point of contact
through which
all the client requests go through.
Krishna
On Nov 16, 2007 10:24 PM, leesquare <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi,
>
> I am trying to find out what is the concurrent write-access
> resolution mechanism in afr. Would appreciate any description
> or pointers to descriptions.
>
> Thanks!
>
> -- Li
>
>
>
>
>
>
>
>
>
> ____________________________________________________________________________________
> Be a better pen pal.
> Text or chat with friends inside Yahoo! Mail. See how.
> http://overview.mail.yahoo.com/
> _______________________________________________
> 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
