Easier serialization of Lock about node-redlock HOT 4 OPEN

Hey @iamnewspecies! This is intentional. Due to the distributed nature of these locks, it is possible for a current lock to expire and a new one to be issued between the time your “unlock” command is issued and the time it hits the redis server. To prevent the command from unlocking the wrong lock (and invalidating all the guarantees of this software), it atomicly checks that the ID is correct before unlocking.

It would be quite unsafe to remove the lock based solely on the resource name.

If you want a more in-depth discussion of the redlock algorithm check out this article.

from node-redlock.

In our case, our backend instances cannot directly access Redis due to a limitation of our cloud provider. So, we spun up a VM to act as a "lock manager" server - however, we need a way to pass the lock id (not just resource id) back to the client, so that the client can send a separate request to the server with the same id, reconstruct the lock object, and release the same lock, if that makes sense. Is there a way to do this apart from maybe serializing that lock object?

from node-redlock.

@neil-119 that’s an interesting use case for sure. I would definitely be open to a PR that makes this easier, but right now you can create a new Redlock.Lock with resource and value.

from node-redlock.

I have a similar issue as @neil-119.

from node-redlock.