You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: