duspring opened a new issue, #13141: URL: https://github.com/apache/dolphinscheduler/issues/13141
### 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 When executing sh bin/stop all In sh, the master/worker node has no DingDing alarm. It has been tested before that V3.1.0 service stop can send an alarm. I don't know why ### What you expected to happen When executing sh bin/stop all In sh, the master/worker node can receive the DingDing alarm, similar to the previous: [{"type": "MASTER", "host": "/nodes/master/ip: port", "event": "SERVER_DOWN", "warningLevel": "SERIOUS"}] data quality alarm ### How to reproduce After configuring alarms and establishing DingDing alarm groups, execute sh bin/stop all When sh is selected, check whether the master/worker node can receive the DingDing alarm, similar to the previous one: The format of master alarm is as follows: [{"type": "MASTER", "host": "/nodes/master/ip: port", "event": "SERVER_DOWN", "warningLevel": "SERIOUS"}] Data quality alarm The worker alarm is as follows: [{"type": "WORKER", "host": "/nodes/worker/default/192.168.10.1:1234", "event": "SERVER_DOWN", "warningLevel": "SERIOUS"}] Data quality alarm ### Anything else My Zookeeper version uses 3.8.0. The master/worker node has been registered normally ### Version 3.1.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]
