Multiple replicas #13

New issue

Open

opened 2026-08-26 04:49:56 +00:00 by jlxq0 · 0 comments

jlxq0 commented

2026-08-26 04:49:56 +00:00

Owner

Migrated from Plan.md's "Deferred (do not drift into these)" section when that file was retired; open work belongs in issues, not in a file with no state. Nothing here is scheduled and no decision has been taken. Do not start it without an explicit go.

One replica, Recreate rollout, RWO PVC. The storage quota code assumes a single writer: quota check and commit are one serialized transaction holding the index lock through check, atomic write, metadata update and accounting. A second replica breaks that assumption silently, not loudly, so this is not a replicas: 2 change.

It needs shared storage (see the object-storage issue) and a quota design that survives concurrent writers in separate processes.

Migrated from `Plan.md`'s "Deferred (do not drift into these)" section when that file was retired; open work belongs in issues, not in a file with no state. **Nothing here is scheduled and no decision has been taken.** Do not start it without an explicit go. One replica, `Recreate` rollout, RWO PVC. **The storage quota code assumes a single writer**: quota check and commit are one serialized transaction holding the index lock through check, atomic write, metadata update and accounting. A second replica breaks that assumption silently, not loudly, so this is not a `replicas: 2` change. It needs shared storage (see the object-storage issue) and a quota design that survives concurrent writers in separate processes.

jlxq0 added this to the Deferred — needs a decision milestone

2026-08-26 04:49:56 +00:00

jlxq0 added the

deferred

label

2026-08-26 04:49:56 +00:00