Skip to content

Fix the shutdownDelay to occur after status = STOPPING #193

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

Merged
merged 3 commits into from
May 28, 2025

Conversation

rbygrave
Copy link
Contributor

No description provided.

rbygrave added 3 commits May 28, 2025 08:58
There is a regression bug in Helidon that means it isn't performing a graceful shutdown.
Refer: helidon-io/helidon#10156

The 200ms default shutdown delay is a workaround, will change this to default 0 when a Helidon fix is released.
In K8s we need the delay after the actual status has been set to STOPPING. This fixes that.
@rbygrave rbygrave requested a review from SentryMan May 28, 2025 03:59
@rbygrave rbygrave self-assigned this May 28, 2025
Copy link
Collaborator

@SentryMan SentryMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

third time's the charm as they say

@@ -100,10 +100,10 @@ void stop(WebServer delegate) {
if (status == STOPPED) {
log.log(Level.INFO, "already stopped");
} else {
invokeCallbacks(STOPPING);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the fix, need to set STOPPING before performing the shutdown delay.

@rbygrave rbygrave changed the title Feature/delay take3 Fix the shutdownDelay to occur after status = STOPPING May 28, 2025
@rbygrave rbygrave merged commit 057af62 into main May 28, 2025
4 checks passed
@rbygrave rbygrave deleted the feature/delay-take3 branch May 28, 2025 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants