Quartz Clustering - triggers duplicated when the server starts
问题 We are facing an issue while using Quartz 2.1.6 with Spring 3.1 in a clustered setup (with the JDBC data store). Current context: Jobs and CRON triggers are defined in the spring configuration file (see below) overwriteExistingJobs property is set to true in SchedulerFactoryBean, so we don't get new job definitions added to the DB with each deployment. However, after each deployment in the cluster, it seems that each node re-creates the trigger data. For example, if we have 2 triggers