-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Worker thread recovery for the executor #57
Comments
Could you remind the place where the bastion_executor::pool::Pool::recover_async_thread call suppossed to be called? Is somewhere in the System or the Worker struct? |
@Relrin Good news, because we don't need this anymore. Since the recoverable handle is basically triggering the panic machinery and application logic replaces faulty tasks on the fly async threads are continuously running in an ordered fashion. That said we can remove that actually. Here is one of the call stacks of the threads:
|
Therefore the bastion_executor::pool::Pool::recover_async_thread method must be dropped as well, right? |
yes :) |
The executor needs to recover worker threads on internal worker thread panic.
Currently, we continue operation with the rest of the threads that are mapped onto the cores. The panicked thread should be assigned to the same affinity that it left.
This case is very edgy but needed for tolerance.
The text was updated successfully, but these errors were encountered: