Open Wjcccccccccc opened 2 years ago
Hi @Wjcccccccccc For English only. Please translate your issue into English.
Hi @Wjcccccccccc For English only. Please translate your issue into English.
Sorry for that, the issue was edited.
The registryCenter is miss? Try to check it.
Additional infomation:
I start two kinds of jobs A and B in the meantime.
A is scheduled every 5 second with cron */5 * * * * ?
B is scheduled to shutdown A after 5 minutes with a specified time point by cron 00 05 12 12 12 ?
, OneOffJobBootstrap is not suitable here because it needs to trigger by an Event, so I have to use ScheduleJobBootstrap with a specified time point.
now I have a pressure test to start A and B 100 times. sometimes the A and B aren't scheduled, so I find the log
Elastic job: ignored exception for: KeeperErrorCode = NoNode for /jato-web_test/pk_end_2487/sharding/0/instance
I guess it is the slowness of Elasticjob's sharding that impact the job, so the job can't get the instance to execute when the time point is coming.
Bug Report
Create many jobs with Cron
*/5 * * * * ?
But some jobs schedule normally, some don't schedule after the output of starting up,
After I open the DEBUG level log, all jobs that don't schedule have printed those logs.
Which version of ElasticJob did you use?
ElasticJob: 3.0.0 curator: 5.1.0
Which project did you use? ElasticJob-Lite or ElasticJob-Cloud?
ElasticJob-Lite
Reason analyze (If you can)
Our test environment doesn't have this issue, but the production environment does. So I doubt there is some effect of the number of jobs?