curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Stone <pacesysj...@gmail.com>
Subject Re: Shared lock usage
Date Fri, 30 Aug 2013 19:54:09 GMT
Thanks!


On Fri, Aug 30, 2013 at 12:31 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> Curator has the Reaper for this purpose. Allocate a Reaper, start it, and
> add any parent lock paths that you'd like cleaned up.
>
> -Jordan
>
> On Aug 30, 2013, at 12:27 PM, Josh Stone <pacesysjosh@gmail.com> wrote:
>
> I'm using shared locks and just wanted to learn what's the best way to
> clean them up when I'm done. When is the appropriate time to delete the
> node that I use for my lock? Can I delete it right after releasing it?
> Would this possibly cause problems with another process that might be
> waiting on that lock or attempting to concurrently create/acquire a lock on
> that path?
>
> Thanks,
> Josh
>
>
>

Mime
View raw message