ArkURL opened a new issue, #16174: URL: https://github.com/apache/dolphinscheduler/issues/16174
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened I use cluster deploy to deploy dolphinscheduler service to 2 server. server and service running env below: os: centos7 db: postgresql-15.7 zookeeper: 3.7.2 python: python3.6 java: java-11 I deploy the service dolphinscheduler to 2 server and make them both be master-server and worker-server. when use `bash bin/start-all.sh`, every service work well and run perfect, but a few second later, some master-server and worker-server went down, but some workflow still can run. at the first time every server work well.  few seconds later, some server down but some workflow can still run.  how to solve it? here is two server's master-server log file. [dolphinscheduler-master.log](https://github.com/user-attachments/files/15883737/dolphinscheduler-master.log) [dolphinscheduler-master_2.log](https://github.com/user-attachments/files/15883738/dolphinscheduler-master_2.log) ### What you expected to happen service work well and not down. [dolphinscheduler-master_2.log](https://github.com/user-attachments/files/15883753/dolphinscheduler-master_2.log) [dolphinscheduler-master.log](https://github.com/user-attachments/files/15883754/dolphinscheduler-master.log) ### How to reproduce use cluster deploy and make them all master-server and worker-server.then start the service. ### Anything else _No response_ ### Version 3.2.x ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
