[GitHub] [shardingsphere-elasticjob] wsYdd opened a new issue, #2161: When one appliacation instance pod restart, the last compeleted job will executed immediately in other instance not in next tigger time

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

wsYdd opened a new issue, #2161:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/2161

   Version: ElasticJob-Lite 3.0.1
   problem：
   1. Applicatoin in k8s has two instance when failover enabled；
   2. Job execute and has finish in one of instance；
   3. Restart the sharding pod, job will executed in another instance not in next tigger time.
   I think with failover enabled, the job will be sharding in new node and wait to execute


-- 
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.apache.org

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

[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #2161: When one appliacation instance pod restart, the last compeleted job will executed immediately in other instance not in next trigger time

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

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

   You may try ElasticJob 3.0.2. The failover will be triggered only when crashed item which was running.


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