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.
Summary of changes
For rolling restarts of the crateDB pods, we want to notify cratedb with an
alter cluster decommission
1 to allow proper handling of running queries and shard handling:preStop
Lifecycle2 executesdc_util
, which is provided via https://cdn.crate.io/downloads/dc_util_x86_64dc_util
sets the crateDB decommission timeout to720s
and sets decomission force totrue
to force decommission in cases crateDB would roll-back the decomission.termination_grace_period_seconds
on the POD is set to900s
to allow the decommission to finish.In case the statefulset is scaled to
0
(scale down, or manual triggered by an administrator),dc_util
tries to detect that and does NOT trigger analter cluster decommission
and POD Termination is triggered by kubelet sending aSIGTERM
.preStop
seems to behave some what fail-save. Eg. if dc_util is not available or cannot be executed, kubelet continues by sendingSIGTERM
.Checklist
CHANGES.rst
Footnotes
https://cratedb.com/docs/crate/reference/en/latest/sql/statements/alter-cluster.html#decommission-nodeid-nodename ↩
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/ ↩