Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
LockError: Unable to fully release the lock on resource
See original GitHub issueAfter upgrading to v4, I started getting this error LockError: Unable to fully release the lock on resource.
Redis server v=5.0.7. (appears to have the same problems in newer versions as well)
I rolled back to version 3.1.2 for now.
This could be related with #39
Issue Analytics
- State:
- Created 4 years ago
- Reactions:15
- Comments:37 (5 by maintainers)
Top Results From Across the Web
Redlock error in node js - Stack Overflow
Init redlock after client was assigned. Your redlock file will look like: var redis = require('redis'); var Redlock = require('redlock'); ...
Read more >node-redlock - Bountysource
After upgrading to v4, I started getting this error LockError: Unable to fully release the lock on resource . Redis server v=5.0.7 ....
Read more >Redlock | Redis
Be able to release this lock reliably; Not deadlock any resource meaning that a resource should be unlocked after a given time period....
Read more >redlock - npm
...do something here... · unlock your resource when you are done ; resource, ttl, · we failed to lock the resource · we...
Read more >See terminal text. 'Waiting for cache lock' error. How to fix? I'm ...
Close synaptic package manager, and the "sudo apt install" command will automatically continue. You cannot have two different applications ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I finally found out the problem and I resolved it myself. I will have some plan to use another component in order to get rid of such issues.
I now also see the bug in 4.2.0, I want to know which version should I use to avoid this bug?