Implement ingester graceful shutdown #4117
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a
Decommission
RPC to ingesters. By default, ingesters are inReady
status. Upon receiving a decommissioning request, ingesters change their status toDecommissioning
, close all their shards, become read-only and wait for them to be indexed by monitoring calls totruncate
. When the indexing of all the shards is completed, ingesters transition to theDecommissioned
status at which point they become safe to shut down.I also added a
OpenObservationStream
RPC to ingesters, so we can track the status of the decommissioning process. In the future, we can enrich theObservationMessage
object to track more things.How was this PR tested?