distlock | universal component of distributed locks | Key Value Database library

by go-locks Go Version: v1.0.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | distlock Summary

distlock is a Go library typically used in Database, Key Value Database, PostgresSQL applications. distlock has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The universal component of distributed locks in golang , support redis and postgresql

Support

Quality

Security

License

Reuse

Support

distlock has a low active ecosystem.

It has 52 star(s) with 6 fork(s). There are 2 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 1 have been closed. On average issues are closed in 25 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of distlock is v1.0.0

Quality

distlock has no bugs reported.

Security

distlock has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

distlock is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

distlock releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi has reviewed distlock and discovered the below as its top functions. This is intended to give you an instant insight into distlock implemented functionality, and help decide if they suit your requirements.

lockCtx blocks until the value is locked or the given context is canceled .
newOptions creates new options object
New returns a new Distlock .
newLocker returns a new locker
generateValue generates a random string
NewRWMutex returns a new mutex
Factor is an option to set the factor .
Expiry returns an OptFunc that sets the expiry value .
Prefix sets the prefix value .
NewMutex returns a new Mutex

Get all kandi verified functions for this library.

distlock Key Features

No Key Features are available at this moment for distlock.

distlock Examples and Code Snippets

No Code Snippets are available at this moment for distlock.

Community Discussions

Trending Discussions on distlock

Is Redisson getLock() Safe for Distributed Lock Usage?

Does Redis need locking?

Single-instance Redis lock with SETNX

How to save semaphore in Aerospike?

Getting exception on locking the key redis-lock nodejs

QUESTION

Is Redisson getLock() Safe for Distributed Lock Usage?

Asked 2020-Apr-03 at 10:36

Is Redisson's getLock() method good for a distributed use case, and how does it compare to getRedLock()?

Redisson (3.11.x) has several methods to instantiate locks:

RedissonClient.getLock()
RedissonClient.getRedLock()
others like getReadWriteLock(), getFairLock(), etc.

What algorithm does getLock() use, and is it safe for distributed usage? The documentation says:

Implements a non-fair locking so doesn't guarantees an acquire order by threads.

I am looking to compare getLock() to getRedLock(), which appears to use Redlock and is documented at the top-level of Redis' distlock page: https://redis.io/topics/distlock:

This page is an attempt to provide a more canonical algorithm to implement distributed locks with Redis. We propose an algorithm, called Redlock, which implements a DLM which we believe to be safer than the vanilla single instance approach.

...

ANSWER

Answered 2020-Apr-03 at 10:36

Is Redisson's getLock() method good for a distributed use case, and how does it compare to getRedLock()?

All Redisson locks fit for distributed use case. RedLock algorithm assumes that you have lock per master node in cluster. RedLock algorithm is proposition and unfortunately there are no feedbacks of its practice usage. Except of its analisys https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html

What algorithm does getLock() use, and is it safe for distributed usage?

RLock object stored as single object in Redis. Other threads are notified through pubsub listeners if lock released. There is also lockWatchdogTimeout setting allows to define time after which lock will be forced to release if current thread is not alive.

UPDATE Since 3.12.5 version getLock() method returns Lock with improved reliability during failover. getRedLock() has been deprecated.

Source https://stackoverflow.com/questions/60573175

QUESTION

Does Redis need locking?

Asked 2019-Dec-20 at 15:15

I read that Redis is single threaded and all commands are atomic. But there are also references talk about locks in Redis, e.g. https://redis.io/topics/distlock

It is not clear to me why Redis still need locks if it is single threaded. Can someone please explain?

...

ANSWER

Answered 2019-Dec-20 at 15:15

No, Redis doesn't need locking.

Yes, Redis is single-threaded. The locks we are talking about here are not for Redis, but using Redis for a Distributed Lock.

The purpose of a distributed lock is to ensure that among several nodes that might try to do the same piece of work, only one actually does it (at least only one at a time). That work might be to write some data to a shared storage system, to perform some computation, to call some external API, or suchlike.

From: How to do distributed locking

These several nodes are workloads you have on other servers. You are using Redis kind-of as a RAM-shared-memory to implement the lock.

Redis is an excellent choice for a distributed lock because it gives you sub-millisecond latency as it is an in-memory database.

Source https://stackoverflow.com/questions/59426682

QUESTION

Single-instance Redis lock with SETNX

Asked 2019-Jun-13 at 23:59

I need to connect to a single Redis instance from an application client.

Since the client will be replicated in Kubernetes, I'm studying Redis documentation about locks to prevent races between the client replicas.

After some googling and reading around, I zeroed in on these two resources:

the SETNX command described here: https://redis.io/commands/setnx
the Redlock algorithm described here: https://redis.io/topics/distlock

Interestingly the SETNX docs explicitly advise against using SETNX to implement locks, stating that it has basically become obsolete:

The following pattern is discouraged in favor of the Redlock algorithm [...]

We document the old pattern anyway because certain existing implementations link to this page as a reference.

However the Redlock algorithm is specifically tailored for distributed locks, thus when one seeks to lock on multiple Redis instances - they actually refer to multiple masters.

To go a bit further, the library redsync (golang) declares the New function as follows:

...

ANSWER

Answered 2019-Jun-13 at 23:59

Yes, it's true that the Redlock algorithm is designed for a distributed Redis system, and that if you're using a single instance it should be fine to use the simpler locking methods described in the SET and SETNX documentation.

However, a more important point is this: you probably don't need to use locks to avoid conflicts between multiple Redis clients. Redis locks are usually used to secure some external distributed resource (see my answer here for a bit more on this). Within Redis itself locks are generally not necessary; thanks to Redis' single-threaded nature, many commands are already atomic, and you have the ability to use transactions or Lua scripts to compose arbitrarily complex atomic operations.

So my advice is to deisgn your client code to use atomicity to avoid conflict rather than trying to use a lock (distributed or otherwise).

Source https://stackoverflow.com/questions/56589374

QUESTION

How to save semaphore in Aerospike?

Asked 2018-Apr-13 at 18:35

We have been using Aeropsike exentsively as key-value store only. However now I couldn't find a way to actually save a lock in Aeropspike like the way we do in Redis.

I guess, I can always save native application lock as blobs, but that means I will be limited to a particular implementation in my application.

...

ANSWER

Answered 2018-Apr-10 at 16:48

Don't believe you can "save" locks in Aerospike. Any form of locking has to be implemented at the Application level and then you have to deal with the locking client abandoning the lock.

Source https://stackoverflow.com/questions/49754160

QUESTION

Getting exception on locking the key redis-lock nodejs

Asked 2017-Oct-03 at 04:47

When trying to lock the hashkey as follow getting an exception:

I am referring the following docs:

https://redis.io/topics/distlock

https://github.com/mike-marcacci/node-redlock

...

ANSWER

Answered 2017-Oct-03 at 04:47

Never mind, It was my mistake. I missed to prefix 'locks:' to the key.

If anyone struggling with issue, then can refer this, by the way in the documentation it has not been mentioned about prefix 'locks:' to key.

Source https://stackoverflow.com/questions/46520212

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install distlock

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: