Repair MongoDB Change Stream Resume Token Gap

Repair MongoDB Change Stream Resume Token Gap — EVIDENCE-LIMITED REVIEW

Scenario received

A connector restarts after downtime and cannot resume using its stored token.

Evidence inventory

• S1: change stream resume tokens — partial extract described by the requester; original full source not provided here.
• S2: replica set oplog metrics — partial extract described by the requester; original full source not provided here.
• S3: consumer restart logs — NOT PROVIDED; required to validate dependent findings.
• S4: checkpoint persistence code — NOT PROVIDED; required to validate dependent findings.

Case-specific checks

Trace last acknowledged token. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
2.

Compare outage duration with oplog horizon. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
3.

Identify checkpoint ordering races. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
4.

Plan safe replay or resync boundaries. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.

Deliverables

Resume gap chronology. Create an evidence-linked section with observations, missing data, owner and next validation step.

Consumer state repair. Create an evidence-linked section with observations, missing data, owner and next validation step.

Replay consistency test matrix. Create an evidence-linked section with observations, missing data, owner and next validation step.

Acceptance gate

Recovery does not silently omit changes or claim a complete replay without comparison evidence. Do not label this gate passed until supplied source records actually demonstrate it.

Verdict and next action

INCOMPLETE — evidence required. Request S3 and S4 from the authorized owner, reconcile them with S1 and S2, then repeat the four checks and log remaining conflicts. No production change, approval, communication, or test run is claimed.