node-redlock icon indicating copy to clipboard operation
node-redlock copied to clipboard

A node.js redlock implementation for distributed, highly-available redis locks

Results 72 node-redlock issues
Sort by recently updated
recently updated
newest added

I have a function that requests a lock, but it handles some events, so I would like to cancel the lock acquire if one of the events is fired. I...

enhancement
help wanted

Original `redlock` mechanics plays perfectly well in theory, however I've found real-life application to suffer in failure modes. Basic scenario is that we have few concurrent requests to acquire locks,...

enhancement
help wanted

I suspect this might be related to some of the other issues with the bug label, but adding my 2c just in case it provides some clues. I have the...

question

I'm trying to implement a Read/Write lock, which allows multiple readers or one writer to acquire the lock. But Redlock has no way to unlock something with the resource ID,...

question

Is there no function which directly unlocks on the basis of resourceId instead of the current function which needs an instance of Lock to unlock it.

enhancement

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 17.0.45 to 18.8.5. Commits See full diff in compare view [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@types/node&package-manager=npm_and_yarn&previous-version=17.0.45&new-version=18.8.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...

dependencies

Bumps [typescript](https://github.com/Microsoft/TypeScript) from 4.6.4 to 4.8.4. Release notes Sourced from typescript's releases. TypeScript 4.8.4 For release notes, check out the release announcement. For the complete list of fixed issues, check...

dependencies

Fixes #173 Supersedes #214 since types expression needs to come first.

Is there any possible way with the redlock algorithm the enforce FIFO behaviour to resolve subsequent lock in order rather than randomly based on the retry interval?

Bumps [ioredis](https://github.com/luin/ioredis) from 4.28.5 to 5.2.3. Release notes Sourced from ioredis's releases. v5.2.3 5.2.3 (2022-08-23) Bug Fixes type of zscore result should be nullable (#1639) (a3838ae) update to latest profile...

dependencies