astelm/minio
1
0
Fork 0
mirror of https://github.com/pgsty/minio.git synced 2026-09-16 07:24:05 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix(iam): resume site healing after leadership changes

Browse Source 
Keep one healing loop per process across replication configuration reloads. Reacquire leadership after a lease is canceled and allow shutdown while waiting, so temporary quorum loss cannot permanently stop revocation propagation.

Signed-off-by: Feng Ruohang <rh@vonng.com>
This commit is contained in:
Feng Ruohang
2026-09-15 22:16:12 +08:00
parent 709d50a916
commit a0dd7dae9b
3 changed files with 101 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/site-replication/iam-revocations.md
+6
View File
@@ -114,6 +114,12 @@ cache.
## Healing, failures and operational cost
Each process starts one healing loop. Losing its distributed leadership lease
pauses work until leadership is reacquired; it does not permanently terminate
healing. Configuration reloads do not create extra loops. The 30-second interval
starts after leadership is acquired and after each completed pass. Initial lock
retries and endpoint recovery can add further delay; it is not a convergence SLA.
The normal IAM loaders maintain an in-memory index of deletion records and
retained boundaries, without secrets. Healing uses this index; it does not add a
second full walk of `config/iam/` every cycle. Existing full IAM loading still