Geek Answers Handbook

Quartz.net: avoid a huge database, stop future triggers, complete scheduled dump tasks

A few questions for real quartz gurus!

I start Quartz.net and hope for some advice before I get burned:

1) I plan that a bunch of tasks / triggers will go away at a certain time in the future. Upon completion of these tasks, I no longer use the job / trigger information in the database. Is there something I need to do to avoid a huge build-up of the Quartz event database, or will they take care and be automatically deleted?

2) Periodically, various tasks are performed. But sometimes, when I do the actual work, I understand that I no longer want to continue periodic events until the work expires. How to stop all future triggers from an ongoing job?

3) Is there a way to reset all scheduled tasks. Ever kind of like "scheduler.DumpAll () ;-)"?

Thanks in advance!

+4
source share
2 answers

  • See the answer from LeftyX (and my comment): under normal circumstances, when a trigger has no longer trigger time, it is deleted, and when the job has no more triggers, it is deleted

  • You can use scheduler.unschduleJob (), scheduler.deleteJob (), scheduler.pauseJob (), scheduler.pauseTrigger () - depending on the specific behavior that you really want.

  • No.

+4
source

I'm probably late ;-), but I just recently started using Quartz.net. The docs say:

Durable - if a job is non-durable, it is automatically deleted from the scheduler once there are no longer any active triggers associated with it.

so that you can define Durable = false for your given part, and you need to delete it when it expires.

+1
source

More articles:


All Articles