gsharma/leased-lock

Leased lock

The leased lock provides a lock service that can be used in an embedded and distributed manner. The idea is to provide locks that are somewhere between a mutex and a binary semaphore in terms of ownership semantics plus also provide leasing in order for us to not indefinitely hold on to shared resources. Locks come with fencing tokens which should be propagated across applications using the lock service. These fencing tokens allow for safe modifications of shared resources.

The interface provided is simple enough to provide support for more backend implementations based off of a database or a file system.

Usage Manual

leased-lock's Issues

Reentrant lock support

Add support for a reentrant read/write lock which can maintain a pair of associated locks - one for read-only operations and one for writing. The read lock may be held simultaneously by multiple reader processes, so long as there are no writers. The write lock should be exclusive. This lock should allow both readers and writers to reacquire read or write locks in the style of a re-entrant lock. Additionally, a writer should be able to acquire the read lock, but not vice-versa. If a reader tries to acquire the write lock, it should never succeed.

Where the heck are the docs/usage manual?

Heartbeat/liveness support for distributed locks