-
Notifications
You must be signed in to change notification settings - Fork 1
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
Started Runner is already in use #597
Comments
The event timing during a runner migration causes (the last event of) this error. Nomad events
The allocation was rescheduled for another host and started before the old one completely stopped. Path 1: Let's fix this handlingWe might:
Path 2: Let's reconsider
In this case, the We might consider our Nomad Event Handling Architecture. If I remember correctly, it was created when we mapped runners to allocations. Nowadays, we map runners to Jobs. Draft:
|
Thanks for digging into this issue and drafting potential solution paths. As discussed in our meeting, we currently decided to postpone working on this issue further. This decision is based on the assumed complexity for both solutions (especially the second path, of course) and the relatively low number of events we see for this error. Given the current time frame, we hence want to focus on other issues first. |
From hashicorp/nomad#23937 we have learned that the |
Sentry Issue: POSEIDON-5R
The text was updated successfully, but these errors were encountered: