Re: Concurrent access of the object via Rados API...

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

 



On Tue, 17 Feb 2015, Dennis Chen wrote:
> Hello,
> 
> For the case of multiple clients(separate process) accessing an object
> in the cluster, is the exclusive protection of the shared object
> needed for the caller?
> 
> Process A::rados::ioctx.write(obj, ...)
> Process B::rados::ioctx.write(obj, ...)

This is correct.  Racing reads/writes get ordered when they arrive at the 
OSD, and we make sure that updates are atomic and durable despite any 
OSD/disk/network failures.

sage



> 
> or:
> 
> Process A::
>     mylock.lock();
>     ioctx.write(obj, ..)
>     mylock.unlock()
> 
> Process B::
>     mylock.lock();
>     ioctx.write(obj, ..)
>     mylock.unlock()
> 
> which one is correct?
> 
> -- 
> Den
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux