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

liquidator: forcefully exit process if snapshot job die #924

Merged
merged 2 commits into from
Apr 1, 2024

Conversation

farnyser
Copy link
Contributor

No description provided.

tokio::spawn(async move {
let res = snapshot_job.await;
tracing::error!("Snapshot job exited, terminating process.. ({:?})", res);
std::process::exit(-1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this works technically, the previous pattern was to collect all the essential jobs in main and do the "something aborted, exit" logic there. I'd prefer that to be consistent.

Secondly, while this addresses the issue with the snapshot job dying unnoticed, the underlying issue is the .expect() on the result of the get_epoch_info rpc call, as far as I remember. Since it's only affecting startup, I'm ok with the restart-to-retry approach for now though.

@farnyser farnyser merged commit 2520c7d into dev Apr 1, 2024
13 checks passed
@farnyser farnyser deleted the serge/liquidator-exit-if-snapshot-job-die branch April 1, 2024 12:45
farnyser added a commit that referenced this pull request Apr 4, 2024
* liquidator: forcefully exit process if snapshot job die

* client: return snapshot_job join handle so it can be watched for early unexpected exit

(cherry picked from commit 2520c7d)
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.

3 participants