-
Notifications
You must be signed in to change notification settings - Fork 1
Persist filesystem WAL writer-epoch fencing across host restarts #714
Copy link
Copy link
Closed
Labels
bad-codeKnown code smell or defect filed for laterKnown code smell or defect filed for laterlegend:testMethod legend test.Method legend test.priority:highMethod priority high.Method priority high.roadmap-a1Roadmap A.1: bounded Hello external effectsRoadmap A.1: bounded Hello external effectsruntimeRuntime coreRuntime corespecSpec/Design documentSpec/Design documenttoolingTooling/CI/CLITooling/CI/CLItype:bugMethod work type bug.Method work type bug.
Description
Metadata
Metadata
Assignees
Labels
bad-codeKnown code smell or defect filed for laterKnown code smell or defect filed for laterlegend:testMethod legend test.Method legend test.priority:highMethod priority high.Method priority high.roadmap-a1Roadmap A.1: bounded Hello external effectsRoadmap A.1: bounded Hello external effectsruntimeRuntime coreRuntime corespecSpec/Design documentSpec/Design documenttoolingTooling/CI/CLITooling/CI/CLItype:bugMethod work type bug.Method work type bug.
Defect
FilesystemWalStore::openreconstructs no writer-epoch state. External-action hosts therefore reacquire a static epoch with fixed fencing, process, host, and lease identities and no previous-epoch linkage on every process invocation. The store validates only in-memory epoch state, so durable request/claim/settlement processes do not prove fresh fencing or a persisted epoch chain.Observed by flyingrobots/hello-echo#24. Blocks flyingrobots/hello-echo#11.
Acceptance
Hello Echo must consume the public contract rather than reconstructing epoch state.