sdlzhd opened a new issue #1934: URL: https://github.com/apache/shardingsphere-elasticjob/issues/1934
## Bug Report ### Which version of ElasticJob did you use? 2.1.5 ### Which project did you use? ElasticJob-Lite or ElasticJob-Cloud? ElasticJob-Lite ### Expected behavior ElasticJob is available after DNS to be restored ### Actual behavior ElasticJob is down ### Reason analyze (If you can) If I use ip to connect to zkp, a `NodeExistsException` will be thrown when the network is disconnected. And ElasticJob will ignore the `NodeExistsException` in `RegExceptionHandler` class. But if I use domain to connect to zkp, When the network is restored, but the DNS server has not been restored, an exception IllegalArgumentException(A HostProvider may not be empty) will be thrown. And 'RegExceptionHandler' will throw the `RegException(IllegalArgumentException)`. ElasticJob can no longer resume. ### Steps to reproduce the behavior. #### use ip ```xml <!-- Ignore other parameters --> <reg:zookeeper id="regCenter" server-lists="192.168.1.100" /> ``` 1. start application 2. disable network 3. resume application #### use domain > hosts > 192.168.1.100 zkp.demo.io ```xml <!-- Ignore other parameters --> <reg:zookeeper id="regCenter" server-lists="zkp.demo.io" /> ``` 1. start application 2. disable network 3. delete hosts -> `192.168.1.100 zkp.demo.io` 4. resume application -- 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]
