I'm trying to figure out the best way to setup our scheduler. We have tons of 2-4 second jobs and I'm trying to get a hot-hot backend of the scheduler. That is, if 1 scheduler goes down, I'd like another scheduler to pickup those jobs automatically. From what I understand, clustering works well when you have long running jobs, but not short. I've read you can schedule jobs in independent schedulers, say 50% in A and 50% in B, and that's ok, but still when A goes down, B won't pickup A's jobs.
Can someone suggest a route here so that I can have multiple quartz schedulers on multiple boxes (backed by jdbc) and when one of those boxes goes down, the scheduler on the other running box continues without a hiccup?
Any help is appreciated.