Deploy a folder with 20.000 job configuration at once.
JobScheduler reads, initializes and loads the configurations correctly, but the EventQueue for FileBasedEvents gets "TORN". Therefore a lot of information for these configurations are not transferred to the reporting database.
- A "TORN" Event is fired by the event queue.
- Tested with PostgreSQL and MySQL
- There is no information about a torn event queue in the scheduler.log
A Deployment of a large sum of configuration files should not result in a torn event queue.
If an event queue is torn, a log entry should be written to the scheduler.log.
Split the deployment of new files into smaller chunks of 3000 items max.