Skip to main content
Announcements
Accelerate Your Success: Fuel your data and AI journey with the right services, delivered by our experts. Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
JerryMac
Contributor
Contributor

Quartz and multiple instances kicking off.

When using cron/quartz, we have an issue when kicking off 100+ jobs at the same time. Some days there is no issue but other days we have several of the jobs kick off twice. The one instance is tracked as normal in the TAC, but the other one runs on the job server but isn't visible in the TAC anywhere. The second job does log to the file system on the job server, just not tracked in the TAC.

We are having this issue mostly when running clustered TACs and Job Servers. We've tried running one TAC, and this does cause less issue but it still happens. Although not sure that matters, because we want to run multiple TACs anyway.

We've tried working with Talend Support to tweak the Quartz Settings, but nothing seems to make a difference.

We've considered creating lock files to avoid the issue, but that seems to be a hack way to solve something that shouldn't be an issue.

Also considered more TACs, though not sure the job volume warrants that yet.

Anyone have this issue and solved it?

Thanks.

Labels (2)
0 Replies