Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Prover] Orchestrator persists partial proving state as proofs are generated #9528

Closed
alexghr opened this issue Oct 29, 2024 · 0 comments · Fixed by #10174
Closed

[Prover] Orchestrator persists partial proving state as proofs are generated #9528

alexghr opened this issue Oct 29, 2024 · 0 comments · Fixed by #10174
Assignees
Milestone

Comments

@alexghr
Copy link
Contributor

alexghr commented Oct 29, 2024

The orchestrator must maintain its own database of proofs so that it's able to recover in the event of a crash:

  • store partial proving state (for each block, for each tx)
  • restore database on boot
  • ask the broker about status of each unfinished proving job
  • continue on from where it left off
@alexghr alexghr changed the title Orchestrator persists partial proving state as proofs are generated [Prover] Orchestrator persists partial proving state as proofs are generated Oct 29, 2024
@alexghr alexghr self-assigned this Oct 29, 2024
@alexghr alexghr added this to A3 Oct 29, 2024
@github-project-automation github-project-automation bot moved this to Todo in A3 Oct 29, 2024
@alexghr alexghr added this to the TestNet milestone Oct 29, 2024
@alexghr alexghr linked a pull request Nov 26, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant