quartz cluster - sergeyzolotukhin/learn-java-gradle GitHub Wiki
Each node in a Quartz cluster is a separate Quartz application that is managed independently of the other nodes. This means that you must start and stop each node individually.
Unlike clustering in many application servers, the separate Quartz nodes do not communicate with one another or with an administration node. Instead, the Quartz applications are made aware of one another through the database tables.



Reasons you may want to do this:
-
For managing resources - e.g. if you have a mix of light-weight and heavy-weight jobs, then you may wish to have a scheduler with many threads to service the lightweight jobs and one with few threads to service the heavy-weight jobs, in order to keep your machines resources from being overwhelmed by running to many heavy-weight jobs concurrently.
-
To schedule jobs in one application, but have them execute within another (when using JDBC-JobStore).