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
There was a pid leak detected by mlab3.fln01
https://github.com/m-lab/ops-tracker/issues/1204
After investigation of the log, the pid leak was caused by scamper after scamper-daeon failed:
The text was updated successfully, but these errors were encountered:
You can see the green line (scamper daemon died), then scamper was brought up, the pid leak started.
After about 11 hours, the pid leak caused the crash of the evrything.
Before we nail down the pid leak in scamper, we will replace the flag
"scamper-daemon-with-scamper-backup"
with
"scamper-daemon"
k8s-support PR following.
Sorry, something went wrong.
https://github.com/m-lab/k8s-support/pull/509/files
The PID count over the same time period as "scamper" was active in the image above.
No branches or pull requests
There was a pid leak detected by mlab3.fln01
https://github.com/m-lab/ops-tracker/issues/1204
After investigation of the log, the pid leak was caused by scamper after scamper-daeon failed:
The text was updated successfully, but these errors were encountered: