[sheepdog] [PATCH 1/4] sheep: fix typo in help information

MORITA Kazutaka morita.kazutaka at gmail.com
Wed Nov 27 05:15:26 CET 2013


At Tue, 26 Nov 2013 16:38:01 +0800,
Robin Dong wrote:
> 
> > Getting a distributed lock is an expensive operation and it can causes
> > a severe performance problem if we do it for each object creation.
> > Can we find another way?  Sheepdog is not designed to allow concurrent
> > write access.
> >
> 
> It will hurt performance if the object is very small, but for big object
> (1GB,10GB,100GB), we only need to lock at "create object inode" moment,
> after that, the object-uploading operation do not need the lock.
> 
> I have tested this zookeeper lock, it could lock/unlock 200 times per
> second, which I think is not too slow even for small objects.

Can it scale when there are many containers who need distributed lock?

Is there any chance the distributed lock support corosync users?

Thanks,

Kazutaka



More information about the sheepdog mailing list