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

docs: record metadata-lock rolling-upgrade limits

Browse Source 
State that old cors-config.lock and new metadata.lock do not interoperate during a rolling upgrade, while the unchanged on-disk format remains rollback-compatible.

Signed-off-by: Feng Ruohang <rh@vonng.com>
This commit is contained in:
Feng Ruohang
2026-09-02 01:16:18 +08:00
parent b3a6d5dbf8
commit 1c2f59604d
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/site-replication/CORS-LWW-DESIGN.md
+7
View File
@@ -297,6 +297,13 @@ avoids a peer reload that needs migration from waiting on a lock held by the
notifying node. Reordered cross-site delivery is handled by the total-order notifying node. Reordered cross-site delivery is handled by the total-order
join. join.
The lock name changes from `cors-config.lock` to `metadata.lock`. During a
rolling upgrade, old and new nodes therefore do not serialize metadata writers
with each other; the shared-lock guarantee begins only after every node in the
cluster runs the new binary. Operators should avoid bucket-metadata changes
during that window. The on-disk record is unchanged, so rollback remains
format-compatible.
## Dispatch and Retry ## Dispatch and Retry
PUT sends a typed `SRBucketMetaTypeCorsConfig` event with canonical base64 XML PUT sends a typed `SRBucketMetaTypeCorsConfig` event with canonical base64 XML