generated from TBD54566975/tbd-project-template
-
Notifications
You must be signed in to change notification settings - Fork 7
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
ps cmd can show inaccurate state #1046
Comments
Open
There's a window in between when a runner is terminated and when it is cleaned up, could that be what you're seeing? |
I think the steps to repro are when a runner loses connection or doesn't end cleanly. I'm imitating that by:
Then bring up replicas and then reduce them down (so that we trigger the above pseudo runner crash)
After this:
|
matt2e
added a commit
that referenced
this issue
Mar 12, 2024
fixes #1046 Runners that were found to have died (rather than cleanly being killed) end up with deployment_id & module_name not set to null. Changes: - removes all dead runners from showing in the `ps` command - correctly updates `deployment_id` and `module_name` to null in the following cases: - Runner terminates unexpectedly - Runner is stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes old runners are shown for deployments.
Working on getting steps to repro
The text was updated successfully, but these errors were encountered: