We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In #612, we noticed that the Nomad Agents are being caught in a crash loop, when too many allocations are being migrated (in response to a restart).
We find OOM killing errors (telegraf, systemd) and Nomad errors.
The text was updated successfully, but these errors were encountered:
Having telegraf running and Nomad not, the server idles around.
Nomad starts successfully (when the server does not want to schedule many allocations on that agent)
Up to 60 runners, the agent works fine.
When requesting 80 runners, the agent crashes.
down
Disabling telegraf
Restarting the node
When starting Nomad, the agent still crashes
It normalizes when restarting Docker and Nomad
Therefore, telegraf does not seem to have a huge impact on the observed behavior
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
In #612, we noticed that the Nomad Agents are being caught in a crash loop, when too many allocations are being migrated (in response to a restart).
We find OOM killing errors (telegraf, systemd) and Nomad errors.
The text was updated successfully, but these errors were encountered: