hiSandog commented on issue #2490: URL: https://github.com/apache/shardingsphere-elasticjob/issues/2490#issuecomment-4849799850
Misfire behavior is easiest to reason about with a concrete timeline. It would help to include the cron expression, job sharding count, whether the job was disabled or the executor was down, and the expected trigger times that were missed. Then the answer can distinguish “run once after recovery” from “catch up every missed fire,” which are very different semantics. -- 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]
