xyhmnb opened a new issue, #20785: URL: https://github.com/apache/pulsar/issues/20785
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version the cluster has three brokers. version:2.10.3 ### Minimal reproduce step we use the command: pulsar-brokers list use, found had two brokers. but the offline broker`s 6650 and 8080 port was alived. then, we want to restart this broker, use the command: pulsar-daemon restart broker. the console show: "Shutdown is in progress... Please wait... Shutdown is in progress... Please wait... Thread dumps are taken for analysis at /usr/local/apache-pulsar-2.10.3/logs/broker.out WARNNING : broker is not stopped completely." now,we found the 8080 port was closed,but the 6650 port was still alived. we used the command:./pulsar-daemon restart broker --force ,to recover the broker. ### What did you expect to see? i want to know why the broker cannot restart properly. what should we do next time. no use --force ### What did you see instead? [broker.txt](https://github.com/apache/pulsar/files/12023255/broker.txt) ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
