user.email fcc7bd04c6 cluster: bound each DistributedLock attempt ...

A lock-ring member reachable from the masters but not from this filer
makes one DistributedLock attempt wait out the TCP connect timeout, so a
write whose key hashes to it stalls far past noLockServerRetryPeriod
before failing. Give the attempt a 10s context deadline so the retry
window can take effect; a timed-out attempt keeps no renew token, so the
lock server still grants the key to at most one owner.

2026-10-26 17:38:19 -07:00

..

lock_manager

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

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

maintenance

admin: auto migrating master maintenance scripts to admin_script plugin config (#8509)

2026-03-04 22:11:07 -08:00

admin_locks.go

Disable master maintenance scripts when admin server runs (#8499)

2026-03-04 00:40:40 -08:00

cluster_test.go

filer: rebuild peer metadata subscriptions after a master reconnect (#10648)

2026-08-08 10:28:25 -07:00

cluster.go

filer: rebuild peer metadata subscriptions after a master reconnect (#10648)

2026-08-08 10:28:25 -07:00

group_members.go

chore: execute goimports to format the code (#7983)

2026-01-07 13:06:08 -08:00

lock_client_test.go

cluster: bound each DistributedLock attempt

2026-10-26 17:38:19 -07:00

lock_client.go

cluster: bound each DistributedLock attempt

2026-10-26 17:38:19 -07:00

lock_ring_manager_test.go

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

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

lock_ring_manager.go

fix: clone protobuf snapshots without copying internal locks (#11968)

2026-10-22 18:38:33 -07:00

master_client.go

filer: announce to master only once gRPC serves, and leave before it stops (#11700)

2026-10-11 21:10:46 +08:00