Skip to content

Restore Omes execution state and outcomes across load-driver restarts - #557

Draft
lilydoar wants to merge 19 commits into
mainfrom
lilydoar/oss-nightlies-recovery
Draft

lilydoar wants to merge 19 commits into
mainfrom
lilydoar/oss-nightlies-recovery

Conversation

@lilydoar

Copy link
Copy Markdown
Contributor

What changed?

Add acknowledged journals for Omes iteration identity, operation recovery and terminal outcomes. Bind Go throughput self-actions to their owning execution, restore frozen starts and operation deadlines after driver restarts, and expose separate probe/scheduler recovery budgets.

Review: Commit by commit, from self-action binding through journal recovery, budget options and fault qualification. This integration includes the open original-start recovery (#539) and scheduler recovery (#542) dependencies.

Why?

A restarted load driver can lose outcomes or regenerate execution state. During intentional faults this can create idle replacement workflows, abandon pending operations or report incomplete counts as a passing failure rate. Recovery needs the same durable record for continuation and acceptance.

How did you test it?

  • Covered by existing tests.
  • Added journal fencing, immutable-intent, lost-acknowledgement, exact-run and interrupted operator/scheduler tests.
  • Tested with native Temporal: control-worker eviction at 225 lanes retained 452 successful iterations and exactly 452 target executions; rollover and graceful stop retained 6/6.

Potential risks

Synchronous journal acknowledgements can reduce offered load; sustained-load and namespace-capacity qualification remain. Ambiguous mutations without proof remain unknown. The journaled worker protocol currently supports Go. The SDK pin and CI build metadata retain the SaaS-compatible Go SDK until its server dependency can adopt the newer version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant