Merge pull request #40 from max0d41/master

Allow unlimited retries to acquire the lock with `retryCount=-1`.
mike-marcacci · Mar 18, 2018 · 479e3bc · 479e3bc
2 parents f8c696a + d80c901
commit 479e3bc
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -34,6 +34,8 @@ Redlock cannot tell you *with certainty* if a resource is currently locked. For
 
 That said, for many tasks it's sufficient to attempt a lock with `retryCount=0`, and treat a failure as the resource being "locked" or (more correctly) "unavailable",
 
+With `retryCount=-1` there will be unlimited retries until the lock is aquired.
+
 
 Installation
 ------------

diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "redlock",
-  "version": "3.1.1",
+  "version": "3.1.2",
   "description": "A node.js redlock implementation for distributed redis locks",
   "main": "redlock.js",
   "scripts": {

diff --git a/redlock.js b/redlock.js
@@ -335,7 +335,7 @@ Redlock.prototype._lock = function _lock(resource, value, ttl, callback) {
 				return lock.unlock(function(){
 
 					// RETRY
-					if(attempts <= self.retryCount)
+					if(self.retryCount === -1 || attempts <= self.retryCount)
 						return setTimeout(attempt, Math.max(0, self.retryDelay + Math.floor((Math.random() * 2 - 1) * self.retryJitter)));
 
 					// FAILED