liaotian1005 opened a new pull request, #13548:
URL: https://github.com/apache/dolphinscheduler/pull/13548

   Master Service fails to tolerate faults when zookeepr recovers:
   When the zookeepr service is shut down(bin/zkServer.sh stop), the master 
will throw a message indicating that the connection to zookeepr times out. 
   
   ```
   org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read 
additional data from server sessionid 0x1005793a4050000, likely server has 
closed socket
        at 
org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:77)
        at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1282)
   ```
   
   
   When zookeepr is recovers, the master service is stopped due to a fault 
recovery failure.
   ```
   [ERROR] 2023-02-11 16:23:15.011 +0800 
org.apache.dolphinscheduler.server.master.registry.MasterWaitingStrategy:[105] 
- Recover from waiting failed, the current server status is RUNNING, will stop 
the server
   org.apache.dolphinscheduler.remote.exceptions.RemoteException: 
NettyRemotingServer bind 5678 fail
        at 
org.apache.dolphinscheduler.remote.NettyRemotingServer.start(NettyRemotingServer.java:144)
        at 
org.apache.dolphinscheduler.server.master.rpc.MasterRPCServer.start(MasterRPCServer.java:108)
        at 
org.apache.dolphinscheduler.server.master.registry.MasterWaitingStrategy.reStartMasterResource(MasterWaitingStrategy.java:130)
        at 
org.apache.dolphinscheduler.server.master.registry.MasterWaitingStrategy.reconnect(MasterWaitingStrategy.java:97)
        at 
org.apache.dolphinscheduler.server.master.registry.MasterConnectionStateListener.onUpdate(MasterConnectionStateListener.java:55)
        at 
org.apache.dolphinscheduler.plugin.registry.zookeeper.ZookeeperConnectionStateListener.stateChanged(ZookeeperConnectionStateListener.java:49)
   
   
   
   
   
   


-- 
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]

Reply via email to