@beignet/provider-locks-redis 0.0.49 → 0.0.50
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +8 -0
- package/README.md +12 -5
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# @beignet/provider-locks-redis
|
|
2
2
|
|
|
3
|
+
## 0.0.50
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 4be4573: Keep mail content out of provider instrumentation, document the Redis
|
|
8
|
+
deployment policy required for monotonic fencing, and align generated agent
|
|
9
|
+
guidance with optional seed, worker, and migration paths.
|
|
10
|
+
|
|
3
11
|
## 0.0.49
|
|
4
12
|
|
|
5
13
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -161,11 +161,18 @@ REDIS_LOCKS_TEST_URL=redis://localhost:6379 bun run test:live
|
|
|
161
161
|
|
|
162
162
|
## Deployment notes
|
|
163
163
|
|
|
164
|
-
Use a single Redis primary with persistence
|
|
165
|
-
that depends on
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
164
|
+
Use a dedicated single Redis primary with persistence, predictable latency, and
|
|
165
|
+
`maxmemory-policy noeviction` for work that depends on fencing tokens. The
|
|
166
|
+
fencing counter has no TTL; an `allkeys-*` eviction policy can delete it and
|
|
167
|
+
allow a later `INCR` to restart at `1`. Beignet supports `noeviction` as the
|
|
168
|
+
production policy so memory pressure fails the lock operation instead of
|
|
169
|
+
silently reusing a fencing token. Verify the policy in the Redis deployment
|
|
170
|
+
configuration rather than relying on application startup access to `CONFIG`.
|
|
171
|
+
|
|
172
|
+
The provider's two-key Lua acquisition does not currently support Redis
|
|
173
|
+
Cluster. Primary failover with asynchronous replication can lose recent lease
|
|
174
|
+
or fencing-counter writes, and the live suite does not simulate failover or
|
|
175
|
+
network partitions.
|
|
169
176
|
|
|
170
177
|
Fencing tokens become a correctness boundary only when the protected durable
|
|
171
178
|
resource atomically accepts tokens strictly greater than the last token it
|