[GitHub] [shardingsphere-elasticjob] misskeyjoy edited a comment on issue #2009: The application service is connected to the elastic job. After the application service is containerized, the corresponding service IP is different every time it is started, resulting in more and more IP lists of servers. For example, after dozens of nodes are restarted for many times, there will be thousands of servers in the job. The more applications are accessed, the more IP addresses of servers stored in ZK nodes, What is a good solution?

[GitBox <gi...@apache.org>]

misskeyjoy edited a comment on issue #2009:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2009#issuecomment-1019687805


   当清理节点后，可能在某些情况会导致分片执行错误。
   案例:
    1. 测试环境正常启动任务
    2. 本地启动任务，并加上disable =true 参数，后本地不跑任务，后续长时间待机，导致这个ip被清理，然后重新使用，导致重新生成了一个没有带disable 参数的 ip 接点，当任务执行的时候，分片会作用到本地这台机器，然后本地 就启动了任务


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org