Re: concurrent write-access resolution in afr

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <leesquare@xxxxxxxxx> 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
> Gluster-devel@xxxxxxxxxx
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux