-
Notifications
You must be signed in to change notification settings - Fork 714
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
Pipe server goes nuts sometimes #3684
Labels
performance
Excessive resource usage and latency; usually a bug or chore
Comments
Possibly related: today a single pipe server with 10,000 goroutines. Top of goroutine dump:
Tail of logs:
|
I tracked this down to the handling of EOF on the non-websocket side of the conversation in the probe. Can reproduce easily by clicking on the 'describe' button on a Kubernetes object. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is observed in multi-tenant mode; all replicas are spinning with high CPU consumption in
multitenant.(*consulPipeRouter).watchAll()
. Consul is also showing high CPU.Logs at the start of the high-cpu period:
the creating/deleting cycle continues, with different tenant IDs appearing from time to time. The 'error CASing' message reappear every so often, sometimes up 2-3 minutes between batches.
According to monitoring data we have experienced periods of high CPU in the pipe service for months.
The text was updated successfully, but these errors were encountered: