node-redlock
node-redlock copied to clipboard
A node.js redlock implementation for distributed, highly-available redis locks
Hi, We are using redlock in a big project, and I started looking into upgrading since we want to upgrade ioredis to v5. A few suggestions: 1. can we have...
I am experiencing an issue where Redlock appears to get stuck when trying to acquire a lock in a Redis cluster environment. This problem does not occur when using a...
I'm experiencing an issue with using Redlock in a Redis cluster environment where the client frequently encounters MOVED errors. The current implementation does not seem to handle these errors correctly,...
When the 'aborted' signal is given, am I right to assume there's some certainty about the lock no longer being valid? Currently `Redlock.using` will spend time trying to release the...
Hello! Thanks for making this package! It seems that typings are broken when tsconfig sets module resolution to bundler. Here's a repository with a reproduction: https://github.com/steelbrain/bug-reproduction-2024-10-redlock Here's the error message...
Occasionally the lock expiry works, but most of the time it doesn't. This test fails 90% of the time. ``` it("won't lock twice", async () => { const lockKeyD =...
If you run acquire([a,b]) and acquire([b,a]) this can deadlock. A simple precaution is to sort the list of resources first to ensure they're always acquired in the same order. Or...
My package's version: redlock: 5.0.0-beta.2 ioredis: 5.4.1 redis server: 7.4.0 node: v22.6.0 My code: ``` const express = require("express"); const Redlock = require("redlock").default; const { promisify } = require("util"); const...
Going trough the Readme, it made me think that `senderId` and `recipientId` were something specific to the redlock paradigm that I needed to know, instead they are just generic identifiers...