-
Notifications
You must be signed in to change notification settings - Fork 16
Allow more time for the etcd cluster to start up #290
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
base: main
Are you sure you want to change the base?
Conversation
WalkthroughThe Changes
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (1.64.8)level=warning msg="The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar." 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (7)
🔇 Additional comments (1)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
internal/controller/factory/statefulset.go (1)
414-416
: StartupProbe tweak is OK, but hard-codedFailureThreshold
= 10 may still be tight for large clustersWith
PeriodSeconds: 5
the probe will abort after ~50 s of failures. Cold boots on I/O-bound disks or large data directories can take longer, so hard-coding this value might re-introduce flakiness.
Consider either
- exposing the threshold (or a full
StartupProbe
template) as part of the CRD spec, or- bumping
FailureThreshold
and/orPeriodSeconds
further (or addingTimeoutSeconds
) based on cluster size / storage class performance.This keeps the operator flexible without a code change for each environment.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
internal/controller/factory/statefulset.go
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
- GitHub Check: pre-commit
- GitHub Check: test-e2e on k8s penultimate version
- GitHub Check: test-e2e on k8s latest version
- GitHub Check: test-e2e on k8s previous version
- GitHub Check: test on k8s latest version
- GitHub Check: test on k8s previous version
- GitHub Check: test on k8s penultimate version
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
This change increases the startupProbe’s failureThreshold from the default value of 3 to 10.
With a probe every 5 seconds, that gives etcd up to 50 seconds to start.
In one of my clusters, etcd becomes ready in about 25 seconds.
Summary by CodeRabbit