austgh opened a new issue, #2113: URL: https://github.com/apache/shardingsphere-elasticjob/issues/2113
The machine has five shards, and the job is scheduled to be executed for 1 minute. One of the jobs was executed for 5 minutes because of too much data. It was found that within five minutes, the other jobs were executed only once, and the next four were not executed. Different shards should not be affected by the timing of other job seekers. versin 2.1.5 elastic-job-lite. code may be AbstractElasticJobExecutor. process() Using asynchronous to synchronous, if one task is executed for too long, other tasks will wait all the time. -- 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]
