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

Indexer Status frozen as RUNNING if unexpectedly crashes #533

Closed
Tracked by #396
darunrs opened this issue Jan 29, 2024 · 0 comments · Fixed by #550
Closed
Tracked by #396

Indexer Status frozen as RUNNING if unexpectedly crashes #533

darunrs opened this issue Jan 29, 2024 · 0 comments · Fixed by #550
Assignees
Labels
bug Something isn't working

Comments

@darunrs
Copy link
Collaborator

darunrs commented Jan 29, 2024

Indexer Status remains as RUNNING if the executor in Runner crashes in the middle of runFunction invocation. This is because the status is set to STOPPED only if the runFunction invocation fails and its error is caught. So, if the error was somehow not caught and the error was thrown at the Executor class level, it will fail there without any error handling, crashing the worker thread.

To resolve this issue, we need to ensure that StreamHandler is able to write the status and blockheight to postgres if it detects the worker thread failed.

@darunrs darunrs added the bug Something isn't working label Jan 29, 2024
@darunrs darunrs closed this as completed Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant