[GitHub] [shardingsphere-elasticjob] TeslaCN commented 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]

TeslaCN commented on issue #2009:
URL: 
https://github.com/apache/shardingsphere-elasticjob/issues/2009#issuecomment-966937020


   I think creating a scheduled job can fix this issue. Find out the server IP 
not exists under /instances and remove it periodically.


-- 
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-unsubscr...@shardingsphere.apache.org

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