Skip to content
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

rpc error: code = Unavailable desc = Starting #33831

Closed
wolf666666 opened this issue Apr 27, 2024 · 3 comments
Closed

rpc error: code = Unavailable desc = Starting #33831

wolf666666 opened this issue Apr 27, 2024 · 3 comments
Labels
bug question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@wolf666666
Copy link

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.

Title: rpc error: code = Unavailable desc = Starting

Description:

One of the cortex ingester instance was killed by the OOM killer because of the memory limit, then the ingester start to startup. but the ingester is still receive request at the same time, so it generate a lot error message:
"Apr 27 17:16:43 cortex-1.16.0[3069602]: ts=2024-04-27T15:16:43.536890158Z caller=grpc_logging.go:64 level=warn method=/cortex.Ingester/QueryStream duration=55.725µs err="rpc error: code = Unavailable desc = Starting" msg=gRPC"

It seems that the distributor still route request to this ingester instance even it have not startup successfully.
and the client that send request to cortex distributor get error message at the same time:
"Request failed. Status: 500 Body: maxFailure (quorum) on a given error family, rpc error: code = Code(500) desc = addr=xxxxxx:port state=ACTIVE zone=www, rpc error: code = Unavailable desc = Starting
"
expect:
the cortex ingester receive request only when it startup totally.

@wolf666666 wolf666666 added bug triage Issue requires triage labels Apr 27, 2024
@adisuissa
Copy link
Contributor

Is this an issue that should be reported to https://github.com/cortexproject/cortex ?
If it is Envoy related, can you provide a more detailed explanation related to Envoy?

@adisuissa adisuissa added question Questions that are neither investigations, bugs, nor enhancements and removed triage Issue requires triage labels Apr 29, 2024
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label May 29, 2024
Copy link

github-actions bot commented Jun 5, 2024

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

2 participants