UNPKG

redis-semaphore

Version:

Distributed mutex and semaphore based on Redis

github.com/swarthy/redis-semaphore

swarthy/redis-semaphore

49 lines (29 loc) • 1.43 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
### redis-semaphore@5.4.0 - Added `identifierSuffix` option, usefull for tracing app instance which locked resource ### redis-semaphore@5.3.1 - Fixed reacquire expired resource in refresh ### redis-semaphore@5.3.0 - Added `stopRefresh` method - Added `externallyAcquiredIdentifier` optional constructor option - Removed `uuid` dependency ### redis-semaphore@5.2.0 - Added `acquireAttemptsLimit` method ### redis-semaphore@5.1.0 - Added `tryAcquire` ### redis-semaphore@5.0.0 - **Breadking change:** Drop Node.js v10.x, v12.x support - Added `ioredis@5` support ### redis-semaphore@4.1.0 - Added `.isAcquired` property on all locks - Added `onLostLock` constructor option. By default throws unhandled error. ### redis-semaphore@4.0.0 - **Breaking change:** `Mutex`, `Semaphore`, `MultiSemaphore` not longer support `Cluster`. For multi-node case use `Redlock*` instead. - Added `RedlockMutex`, `RedlockSemaphore`, `RedlockMultiSemaphore` - Internals refactored ### redis-semaphore@3.2.0 - Added `MultiSemaphore` ### redis-semaphore@3.0.0 - **Breaking change:** `FairSemaphore` has been removed. Use `Semaphore` instead (has the same "fairness") - the `acquire` method in `Semaphore` no longer returns a boolean. Instead, it throws an error if it cannot acquire, and if it doesn't throw, you can assume it worked. - Internal code has been cleaned up - Added more test, include synthetic node unsynchroned clocks