-
-
Notifications
You must be signed in to change notification settings - Fork 3
fix: Add startupProbe to prevent Superset startup problems #654
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
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.
Just a changelog suggestion, and question for my own understanding.
CHANGELOG.md
Outdated
- Fix container not starting because Superset was starting too slow and was killed because a failing liveness probe. | ||
We now add a proper startup probe, which allows Superset to take longer to start up ([#654]). |
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.
Indenation
- Fix container not starting because Superset was starting too slow and was killed because a failing liveness probe. | |
We now add a proper startup probe, which allows Superset to take longer to start up ([#654]). | |
- Fix container not starting because Superset was starting too slow and was killed because a failing liveness probe. | |
We now add a proper startup probe, which allows Superset to take longer to start up ([#654]). |
But I think it could be briefer:
- Fix container not starting because Superset was starting too slow and was killed because a failing liveness probe. | |
We now add a proper startup probe, which allows Superset to take longer to start up ([#654]). | |
- Add startup probe to give Superset longer to start up than the default ([#654]). |
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.
I prefer the current two sentences as they make a bit clearer what the problem was exactly and what the impact was.
than the default
There is no default, only before (like 60s) and after (~10 minutes) ^^
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.
There is no default, only before (like 60s) and after (~10 minutes) ^^
Where was the 60
defined?
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.
15s initial_delay_seconds + failure_threshold (3) * period_seconds (15s)
Co-authored-by: Nick <[email protected]>
Description
Superset 4.0 and 4.1 both failed to start quick enough on a customer setup on Rhoencloud and crashlooped.
Fixed it via podOverrides, adding the probe to the operator here
Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecation
label & add to the deprecation scheduletype/experimental
label & add to the experimental features tracker