Epic: Phase 2 — Dual Primary Write Mode #162

New issue

Open

opened 2026-03-15 23:08:37 +00:00 by freemo · 0 comments

freemo commented

2026-03-15 23:08:37 +00:00

Owner

Background and Context

In Phase 2 of the GDBM-to-ES migration, both stores must succeed for a write to complete. If the ES write fails after a successful GDBM write, the GDBM write must be rolled back. This ensures the two stores never diverge. Verification tooling confirms store consistency before transitioning to Phase 3.

Demonstrable Outcome

When es_write_mode: :dual_primary, any ES failure triggers GDBM rollback. A verification tool compares all GDBM objects against ES aggregates and reports zero discrepancies.

Acceptance Criteria

:dual_primary mode implemented with rollback
Verification tool detects and reports discrepancies
Full migration verified with zero missing aggregates

## Background and Context In Phase 2 of the GDBM-to-ES migration, both stores must succeed for a write to complete. If the ES write fails after a successful GDBM write, the GDBM write must be rolled back. This ensures the two stores never diverge. Verification tooling confirms store consistency before transitioning to Phase 3. ## Demonstrable Outcome When `es_write_mode: :dual_primary`, any ES failure triggers GDBM rollback. A verification tool compares all GDBM objects against ES aggregates and reports zero discrepancies. ## Acceptance Criteria - `:dual_primary` mode implemented with rollback - Verification tool detects and reports discrepancies - Full migration verified with zero missing aggregates