-
Notifications
You must be signed in to change notification settings - Fork 816
Tens of thousands of gRPC goroutines between ruler and ingester #672
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
Comments
Dump of the server side of these calls (on another occasion):
Reference grpc/grpc-go#1685 (comment) |
Where we used to see this on a 24-36(-ish) hour cadence, we haven't seen it at all since the referenced PRs were merged. We still have some other struggles, per #702, but this particular behavior appears to have reared it's head lately. Is this one close-able, or are there still instances of it cropping up elsewhere? |
Yeah, I think the timeout would have eliminated this one, though perhaps triggered other symptoms. |
Symptom: we occasionally get massive numbers of goroutines in the ruler like this:
There is no timeout on the context used to call
Push()
in the ruler.Looks like the idea was to supply
grpc.WithTimeout()
, but that's a timeout on the dial, not on each individual call. Also it is documented to do nothing unless you also supplyWithBlock
, and we don't.The text was updated successfully, but these errors were encountered: