Re: doozer, zookeeper and file-locking

[Keith Rarick]

If the file is stored on a single machine, it's probably simpler to use
a not-distributed lock and put it on the same machine as the file.

On Mon, Mar 18, 2013 at 11:50 AM, ml <matt....@gmail.com> wrote:
> Hi,
>
> I'm looking for a tool that will allow distributed services access files on
> a file server atomically (i.e. via a file lock). In other words, I have
> service x running as multiple threads or processes possibly on multiple
> hosts, and it needs to process files in a remote file server and no two
> threads should ever be allowed to access the same file at the same time.
> I've been looking at the docs for zookeeper, doozer, and some others and not
> sure which is the appropriate tool. In fact, these all seem like overkill.
> Can anyone provide insights?
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "doozer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to doozer+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>