user.emailandDevin f7684c4478 dlm: replay the current token on a lost renewal's retry ...

A renewal rotates the token server-side before the response is sent. When
that response is lost the client only knows the superseded token: retries
mismatched, the token was cleared, and the holder conflicted with its own
lease until it expired. The lock now remembers the superseded token, so a
retry from the same owner replays the current token, and a superseded
token can still release its own lock.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-10-26 19:30:07 -07:00

..

distributed_lock_manager_test.go

dlm: resilient distributed locks via consistent hashing + backup replication (#8860)

2026-03-30 23:29:56 -07:00

distributed_lock_manager.go

dlm: replay the current token on a lost renewal's retry

2026-10-26 19:30:07 -07:00

hash_ring_test.go

s3: dial the object lock's primary filer directly (#9626)

2026-05-24 00:40:43 -07:00

hash_ring.go

s3: dial the object lock's primary filer directly (#9626)

2026-05-24 00:40:43 -07:00

lock_manager_test.go

dlm: replay the current token on a lost renewal's retry

2026-10-26 19:30:07 -07:00

lock_manager.go

dlm: replay the current token on a lost renewal's retry

2026-10-26 19:30:07 -07:00

lock_ring_prior_test.go

filer: keep a moved key on its prior owner while the ring settles (#11108)

2026-09-02 19:40:53 -07:00

lock_ring_test.go

master,filer: fix lock ring poisoning after leader change (#11453)

2026-09-26 11:57:00 +08:00

lock_ring.go

fix(filer): leave the lock ring before stopping gRPC on shutdown (#11604)

2026-10-06 09:53:40 +08:00