-
Notifications
You must be signed in to change notification settings - Fork 820
HTTP handler for ingester shutdown #1746
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
Conversation
Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>
Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>
55d9f38
to
073ed6a
Compare
Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>
Tested it and it works as intended. Ingester goes to LEAVING states, flushes after waiting for other ingesters, and then leaves the ring. I also added another commit to avoid panic on multiple shutdown calls (during graceful shutdown after having called |
Could you add a description of this API to Also it seems worth mentioning in CHANGELOG.md. |
Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@codesome Will this shutdown cause a clean exit from cortex or only shutdown the ingester module?
Needs rebase for changelog conflict now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after fixing the API nit. And after rebase.
Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>
Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>
This is based on this design for scaling down using the WAL. This would not block #1103 but this is required for scale downs.
I have yet to verify how it will interact with Kubernetes health checks and pod restarts if the endpoint is hit.