-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Broker doesn't get killed when the shutdown exceeds brokerShutdownTimeoutMs #15650
Comments
|
It looks like the BK client blocked on |
Is there more stack info? |
Another case:
|
@Technoboy- The issue where the broker doesn't get killed is separate from the unloadNamespaceBundlesGracefully hanging forever. It's true that the cause might be the unloading hanging forever, but it's another problem that should be addressed. I noticed your PR, but that doesn't really deal with the underlying problem which causes the hanging. |
@Technoboy- I reported #15753 about the unloading hanging. |
The issue had no activity for 30 days, mark with Stale label. |
Describe the bug
Broker should get killed after brokerShutdownTimeoutMs, which is 60 seconds by default.
I have noticed that sometimes broker pods don't get stopped and pods will have to be manually killed.
To Reproduce
I haven't found a way to reproduce the problem.
Expected behavior
Broker should get killed after brokerShutdownTimeoutMs
Additional context
It looks like the brokerShutdownTimeoutMs feature stopped working as expected when MessagingServiceShutdownHook got removed in #12146 .
It would be useful to print out the thread dump to System.out before killing the process with
Runtime.getRuntime().halt(1)
. This could help investigate why the shutdown is stuck.The text was updated successfully, but these errors were encountered: