STORE DOCS / DIAGRAMS

Recovery after backend acceptance

Recovery after backend acceptanceA committed receipt and ACKED phase prevent another push of generation g; failure before that transaction commits leaves INFLIGHT, so a later drain replays g and k, receives the same result, persists the receipt, and resumes local work.ALT[receipt and ACKED transaction commits][failure or death before commit]persist complete receiptand ACKEDadopt echo, apply effects,retire intentRecovery may repeat local work,never push gLast durable phase remains INFLIGHTlater drain replaysgeneration g and key kduplicate requestfor g and ksame authoritative resultsame acknowledgementpersist complete receiptand ACKEDresume adoption, effects,and retirementMutation engineMutationServerBackendCall / local workAcknowledgement / return
This sequence starts after backend acceptance. Once ACKED is durable, recovery can repeat adoption, effects, and retirement but never re-pushes generation g.