Really no difference exists when starting Quartz applications in a cluster. Each instance (or node) must be started individually. On startup, the instance connects to the database, retrieves the Scheduler information, and starts scheduling jobs.
Because Quartz uses a random load-balancing algorithm, you will see jobs being executed by different instances in a random manner. No pattern or predetermined node executes a particular job or execution.
The next section discusses some of the more common problems and tasks when dealing with Quartz in a clustered environment.
Scheduling in the Enterprise
Getting Started with Quartz
Hello, Quartz
Scheduling Jobs
Cron Triggers and More
JobStores and Persistence
Implementing Quartz Listeners
Using Quartz Plug-Ins
Using Quartz Remotely
Using Quartz with J2EE
Clustering Quartz
Quartz Cookbook
Quartz and Web Applications
Using Quartz with Workflow
Appendix A. Quartz Configuration Reference