-
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
Shutting down broker hangs in ModularLoadManagerImpl.disableBroker #15643
Comments
One observation is that LockManagerImpl's asyncClose method doesn't wait for locks to be released: Lines 181 to 185 in 12ca27f
This could cause a race. |
another failure today: https://github.com/apache/pulsar/runs/6483941218?check_suite_focus=true#step:11:531 |
The issue had no activity for 30 days, mark with Stale label. |
recent stack trace:
at https://github.com/apache/pulsar/runs/8026627215?check_suite_focus=true#step:11:77 |
The issue had no activity for 30 days, mark with Stale label. |
This might be fixed by #19055 |
fixed by #15755 |
Tests sporadically get stuck in the broker shutdown sequence. This could also be a production code issue.
Relevant stack traces:
Full thread dump in jstack.review
This seems to be related to a race condition in the shutdown sequence.
pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/PulsarService.java
Lines 443 to 463 in e268d00
In #10365 was moved to run the load manager stop before the broker service close. This seems to cause issues in broker shutdown when unloadNamespaceBundlesGracefully calls load manager's disableBroker method:
pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/BrokerService.java
Lines 890 to 901 in 5db06a1
The text was updated successfully, but these errors were encountered: