Complete steps to build a spring boot + quartz cluster

Quartz cluster capability:

• The quartz cluster is divided into horizontal cluster and vertical cluster. The horizontal cluster will deploy the timing task nodes on different servers. The biggest problem with the horizontal cluster is the clock synchronization problem.
  The quartz cluster strongly requires clock synchronization. If the clock cannot be synchronized, it will cause the state of each node in the cluster to be disordered and cause unpredictable consequences. Please search for the server clock synchronization by yourself.
  If clock synchronization can be ensured, the horizontal cluster can ensure service reliability. If one node is dead or one server is down, the other nodes will still serve normally; if the vertical cluster is deployed on the same server, the cluster nodes are deployed on the same server.
  Clock synchronization is naturally not a problem, but there is a single point of failure problem, and the server downtime seriously affects the availability of services. Therefore, the cluster plan should be considered in light of actual conditions
• Since the cluster strongly requires clock synchronization, local development must not be connected to the online environment whether it is a vertical cluster or a horizontal cluster (local is also a cluster mode). This will inevitably destroy the cluster, but if the local one is in a non-cluster mode,
  Then you can connect to the online environment according to the situation.
• The implementation methods of clusters such as quartz cluster and redis are different. The redis cluster requires communication between nodes, and each node needs to know the status of other nodes. The implementation method of quartz cluster is 11 tables. The cluster nodes do not communicate with each other, but realize the cluster through persistent locking of timed tasks.
• The consequences of destroying the cluster are usually deadlocks or disordered states. Each node is not available or some of the nodes can use some or all of the timing tasks.

The above are some personal insights. Let’s start the main text of this article. This article mainly introduces relevant content about the construction of spring boot + quartz clusters. It is shared for your reference and learning. I won’t say much below. Let’s take a look at the detailed introduction together.

The steps are as follows:

Spring boot bean configuration:

 @Configurationpublic class QuartzConfig { @Value("${quartz.scheduler.instanceName}") private String quartzInstanceName; @Value("${org.quartz.dataSource.myDS.driver}") private String myDSDriver; @Value("${org.quartz.dataSource.myDS.URL}") private String myDSUser; @Value("${org.quartz.dataSource.myDS.password}") private String myDSPassword; @Value("${org.quartz.dataSource.myDS.maxConnections}") private String myDSMaxConnections; /** * Set properties* @return * @throws IOException */ private Properties quartzProperties() throws IOException { Properties prop = new Properties(); prop.put("quartz.scheduler.instanceName", quartzInstanceName); prop.put("org.quartz.scheduler.instanceId", "AUTO"); prop.put("org.quartz.scheduler.skipUpdateCheck", "true"); prop.put("org.quartz.scheduler.jmx.export", "true"); prop.put("org.quartz.jobStore.class", "org.quartz.impl.jdbcjobstore.JobStoreTX"); prop.put("org.quartz.jobStore.driverDelegateClass", "org.quartz.impl.jdbcjobstore.StdJDBCDelegate"); prop.put("org.quartz.jobStore.dataSource", "quartzDataSource"); prop.put("org.quartz.jobStore.tablePrefix", "QRTZ_"); prop.put("org.quartz.jobStore.isClustered", "true"); prop.put("org.quartz.jobStore.clusterCheckinInterval", "20000"); prop.put("org.quartz.jobStore.dataSource", "myDS"); prop.put("org.quartz.jobStore.maxMisfiresToHandleAtATime", "1"); prop.put("org.quartz.jobStore.misfireThreshold", "120000"); prop.put("org.quartz.jobStore.txIsolationLevelSerializable", "true"); prop.put("org.quartz.jobStore.selectWithLockSQL", "SELECT * FROM {0}LOCKS WHERE LOCK_NAME = ? FOR UPDATE"); prop.put("org.quartz.threadPool.class", "org.quartz.simpl.SimpleThreadPool"); prop.put("org.quartz.threadPool.threadCount", "10"); prop.put("org.quartz.threadPool.threadPriority", "5"); prop.put("org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread", "true"); prop.put("org.quartz.dataSource.myDS.driver", myDSDriver); prop.put("org.quartz.dataSource.myDS.URL", myDSURL); prop.put("org.quartz.dataSource.myDS.user", myDSUser); prop.put("org.quartz.dataSource.myDS.password", myDSPassword); System.out.println("myDSMaxConnections:" + myDSMaxConnections); prop.put("org.quartz.dataSource.myDS.maxConnections", myDSMaxConnections); prop.put("org.quartz.plugin.triggHistory.class", "org.quartz.plugins.history.LoggJobHistoryPlugin"); prop.put("org.quartz.plugin.shutdownhook.class", "org.quartz.plugins.shutdownHookPlugin"); prop.put("org.quartz.plugin.shutdownhook.cleanShutdown", "true"); return prop; } @Bean public SchedulerFactoryBean schedulerFactoryBean(@Qualifier("dialogJobTrigger") Trigger cronJobTrigger) throws IOException { SchedulerFactoryBean factory = new SchedulerFactoryBean(); // this allows to update triggers in DB when updating settings in config file: // Used for quartz cluster, QuartzScheduler updates the existing jobs when starting, so that there is no need to delete the qrtz_job_details table after modifying the targetObject. The corresponding record of factory.setOverwriteExistingJobs(true); //Used for quartz cluster, load quartz data source //factory.setDataSource(dataSource); //QuartzScheduler delays startup, after 10 seconds of application startup, QuartzScheduler starts factory.setStartupDelay(10); //Used for quartz cluster, load quartz data source configuration factory.setQuartzProperties(quartzProperties()); factory.setAutoStartup(true); factory.setApplicationContextSchedulerContextKey("applicationContext"); //Register trigger factory.setTriggers(cronJobTrigger);<br data-filtered="filtered"> //Use the configuration file directly// factory.setConfigLocation(new FileSystemResource(this.getClass().getResource("/quartz.properties").getPath())); return factory; } /** * Loading job * @return */ @Bean public JobDetailFactoryBean updateDialogStatusJobDetail() { return createJobDetail(InvokingJobDetailDetailFactory.class, "updateDialogStatusGroup", "dialogJob"); } /** * Load the trigger* @param jobDetail * @return */ @Bean(name = "dialogJobTrigger") public CronTriggerFactoryBean dialogStatusJobTrigger(@Qualifier("updateDialogStatusJobDetail") JobDetail jobDetail) { return dialogStatusTrigger(jobDetail, "0 0 0/1 * * ?"); } /** * Create the job factory* @param jobClass * @param groupName * @param targetObject * @return */ private static JobDetailFactoryBean createJobDetail(Class<?> jobClass, String groupName, String targetObject) { JobDetailFactoryBean factoryBean = new JobDetailFactoryBean(); factoryBean.setJobClass(jobClass); factoryBean.setDurability(true); factoryBean.setRequestsRecovery(true); factoryBean.setGroup(groupName); Map<String, String> map = new HashMap<>(); map.put("targetObject", targetObject); map.put("targetMethod", "execute"); factoryBean.setJobDataAsMap(map); return factoryBean; } /** * Create a trigger factory* @param jobDetail * @param cronExpression * @return */ private static CronTriggerFactoryBean dialogStatusTrigger(JobDetail jobDetail, String cronExpression) { CronTriggerFactoryBean factoryBean = new CronTriggerFactoryBean(); factoryBean.setJobDetail(jobDetail); factoryBean.setCronExpression (cronExpression); return factoryBean; } }

InvokingJobDetailDetailFactory object:

 public class InvokingJobDetailDetailFactory extends QuartzJobBean{ // The class where the scheduled task is located private String targetObject; // The specific scheduled task needs to be executed private String targetMethod; private ApplicationContext ctx; @Override protected void executeInternal(JobExecutionContext context) throws JobExecutionException { try { Object oargetObject = ctx.getBean(targetObject); Method m = null; try { m = oargetObject.getClass().getMethod(targetMethod); m.invoke(otargetObject); } catch (SecurityException e) { e.printStackTrace(); } catch (NoSuchMethodException e) { e.printStackTrace(); } } catch (Exception e) { throw new JobExecutionException(e); } } public void setApplicationContext(ApplicationContext applicationContext) { this.ctx = applicationContext; } public void setTargetObject(String targetObject) { this.targetObject = targetObject; } public void setTargetMethod(String targetMethod) { this.targetMethod = targetMethod; }}

Note: The set method must not be missing. The applicationContext in the setApplicationContext is related to the value filled in factory.setApplicationContextSchedulerContextKey("applicationContext"). The principle is implemented by the BeanWrapper in the InvokingJobDetailDetailFactory parent class.

sql script:--

 <em id="__mceDel">-- Table structure `qrtz_blob_triggers`-- CREATE TABLE IF NOT EXISTS `qrtz_blob_triggers` ( `SCHED_NAME` varchar(120) NOT NULL, `TRIGGER_NAME` varchar(120) NOT NULL, `TRIGGER_GROUP` varchar(120) NOT NULL, `BLOB_DATA` blob) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- `TIME_ZONE_ID` varchar(80) DEFAULT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- `TRIGGER_NAME` varchar(120) NOT NULL, `TRIGGER_GROUP` varchar(120) NOT NULL, `INSTANCE_NAME` varchar(120) NOT NULL, `FIRED_TIME` bigint(13) NOT NULL, `SCHED_TIME` bigint(13) NOT NULL, `PRIORITY` int(11) NOT NULL, `STATE` varchar(16) NOT NULL, `JOB_NAME` varchar(120) DEFAULT NULL, `JOB_GROUP` varchar(120) DEFAULT NULL, `IS_NONCONCURRENT` varchar(1) DEFAULT NULL, `REQUESTS_RECOVERY` varchar(1) DEFAULT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- EXISTS `qrtz_job_details` ( `SCHED_NAME` varchar(120) NOT NULL, `JOB_NAME` varchar(120) NOT NULL, `JOB_GROUP` varchar(120) NOT NULL, `DESCRIPTION` varchar(250) DEFAULT NULL, `JOB_CLASS_NAME` varchar(250) NOT NULL, `IS_DURABLE` varchar(1) NOT NULL, `IS_NONCONCURRENT` varchar(1) NOT NULL, `IS_UPDATE_DATA` varchar(1) NOT NULL, `REQUESTS_RECOVERY` varchar(1) NOT NULL, `JOB_DATA` blob) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- NULL, `LOCK_NAME` varchar(40) NOT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- `CHECKIN_INTERVAL` bigint(13) NOT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- `TRIGGER_GROUP` varchar(120) NOT NULL, `REPEAT_COUNT` bigint(7) NOT NULL, `REPEAT_INTERVAL` bigint(12) NOT NULL, `TIMES_TRIGGERED` bigint(10) NOT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- IF NOT EXISTS `qrtz_simprop_triggers` ( `SCHED_NAME` varchar(120) NOT NULL, `TRIGGER_NAME` varchar(120) NOT NULL, `TRIGGER_GROUP` varchar(120) NOT NULL, `STR_PROP_1` varchar(512) DEFAULT NULL, `STR_PROP_2` varchar(512) DEFAULT NULL, `STR_PROP_3` varchar(512) DEFAULT NULL, `INT_PROP_1` int(11) DEFAULT NULL, `INT_PROP_2` int(11) DEFAULT NULL, `LONG_PROP_1` bigint(20) DEFAULT NULL, `LONG_PROP_2` bigint(20) DEFAULT NULL, `DEC_PROP_1` decimal(13,4) DEFAULT NULL, `BOOL_PROP_1` varchar(1) DEFAULT NULL, `BOOL_PROP_2` varchar(1) DEFAULT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- `TRIGGER_GROUP` varchar(120) NOT NULL, `JOB_NAME` varchar(120) NOT NULL, `JOB_GROUP` varchar(120) NOT NULL, `DESCRIPTION` varchar(250) DEFAULT NULL, `NEXT_FIRE_TIME` bigint(13) DEFAULT NULL, `PREV_FIRE_TIME` bigint(13) DEFAULT NULL, `PRIORITY` int(11) DEFAULT NULL, `TRIGGER_STATE` varchar(16) NOT NULL, `TRIGGER_TYPE` varchar(8) NOT NULL, `START_TIME` bigint(13) NOT NULL, `END_TIME` bigint(13) DEFAULT NULL, `CALENDAR_NAME` varchar(200) DEFAULT NULL, `MISFIRE_INSTR` smallint(2) DEFAULT NULL, `JOB_DATA` blob) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; --- Indexes for dumped tables- --- Indexes for table `qrtz_blob_triggers`--ALTER TABLE `qrtz_blob_triggers` ADD PRIMARY KEY (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`), ADD KEY `SCHED_NAME` (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`); --- Indexes for table `qrtz_calendars`--ALTER TABLE `qrtz_calendars` ADD PRIMARY KEY (`SCHED_NAME`,`CALENDAR_NAME`); --- Indexes for table `qrtz_cron_triggers`--ALTER TABLE `qrtz_cron_triggers`--ALTER TABLE `qrtz_cron_triggers` ADD PRIMARY KEY (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`); --- Indexes for table `qrtz_fired_triggers`--ALTER TABLE `qrtz_fired_triggers` ADD PRIMARY KEY (`SCHED_NAME`,`ENTRY_ID`), ADD KEY `IDX_QRTZ_FT_TRIG_INST_NAME` (`SCHED_NAME`,`INSTANCE_NAME`), ADD KEY `IDX_QRTZ_FT_INST_JOB_REQ_RCVRY` (`SCHED_NAME`,`INSTANCE_NAME`,`REQUESTS_RECOVERY`), ADD KEY `IDX_QRTZ_FT_J_G` (`SCHED_NAME`,`JOB_NAME`,`JOB_GROUP`), ADD KEY `IDX_QRTZ_FT_JG` (`SCHED_NAME`,`JOB_GROUP`), ADD KEY `IDX_QRTZ_FT_T_G` (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`), ADD KEY `IDX_QRTZ_FT_TG` (`SCHED_NAME`,`TRIGGER_GROUP`); --- Indexes for table `qrtz_job_details`--ALTER TABLE `qrtz_job_details` ADD PRIMARY KEY (`SCHED_NAME`,`JOB_NAME`,`JOB_GROUP`), ADD KEY `IDX_QRTZ_J_REQ_RECOVERY` (`SCHED_NAME`,`REQUESTS_RECOVERY`), ADD KEY `IDX_QRTZ_J_GRP` (`SCHED_NAME`,`JOB_GROUP`); --- Indexes for table `qrtz_locks`--ALTER TABLE `qrtz_locks` ADD PRIMARY KEY (`SCHED_NAME`,`LOCK_NAME`); --- Indexes for table `qrtz_paused_trigger_grps`--ALTER TABLE `qrtz_paused_trigger_grps` ADD PRIMARY KEY (`SCHED_NAME`,`TRIGGER_GROUP`); --- Indexes for table `qrtz_scheduler_state`--ALTER TABLE `qrtz_scheduler_state` ADD PRIMARY KEY (`SCHED_NAME`,`INSTANCE_NAME`); --- Indexes for table `qrtz_simple_triggers`--ALTER TABLE `qrtz_simple_triggers` ADD PRIMARY KEY (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`); --- Indexes for table `qrtz_simple_triggers`--ALTER TABLE `qrtz_simple_triggers` ADD PRIMARY KEY (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`); --- Indexes for table `qrtz_triggers`--ALTER TABLE `qrtz_triggers` ADD PRIMARY KEY (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`), ADD KEY `IDX_QRTZ_T_J` (`SCHED_NAME`,`JOB_NAME`,`JOB_GROUP`), ADD KEY `IDX_QRTZ_T_JG` (`SCHED_NAME`,`JOB_GROUP`), ADD KEY `IDX_QRTZ_T_C` (`SCHED_NAME`,`CALENDAR_NAME`(191)), ADD KEY `IDX_QRTZ_T_G` (`SCHED_NAME`,`TRIGGER_GROUP`), ADD KEY `IDX_QRTZ_T_STATE` (`SCHED_NAME`,`TRIGGER_STATE`), ADD KEY `IDX_QRTZ_T_N_STATE` (`SCHED_NAME`,`TRIGGER_NAME`,`TRIGGER_GROUP`,`TRIGGER_STATE`), ADD KEY `IDX_QRTZ_T_N_G_STATE` (`SCHED_NAME`,`TRIGGER_GROUP`,`TRIGGER_STATE`), ADD KEY `IDX_QRTZ_T_NEXT_FIRE_TIME` (`SCHED_NAME`,`NEXT_FIRE_TIME`), ADD KEY `IDX_QRTZ_T_NFT_ST` (`SCHED_NAME`,`TRIGGER_STATE`,`NEXT_FIRE_TIME`), ADD KEY `IDX_QRTZ_T_NFT_MISFIRE` (`SCHED_NAME`,`MISFIRE_INSTR`,`NEXT_FIRE_TIME`), ADD KEY `IDX_QRTZ_T_NFT_ST_MISFIRE` (`SCHED_NAME`,`MISFIRE_INSTR`,`NEXT_FIRE_TIME`,`TRIGGER_STATE`), ADD KEY `IDX_QRTZ_T_NFT_ST_MISFIRE_GRP` (`SCHED_NAME`,`MISFIRE_INSTR`,`NEXT_FIRE_TIME`,`TRIGGER_GROUP`,`TRIGGER_STATE`); --- Limit exported tables --- Limit tables `qrtz_blob_triggers`--ALTER TABLE `qrtz_blob_triggers` ADD CONSTRAINT `qrtz_blob_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`); --- Limit table `qrtz_cron_triggers`--ALTER TABLE `qrtz_cron_triggers` ADD CONSTRAINT `qrtz_cron_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`); --- Restriction table `qrtz_simple_triggers`--ALTER TABLE `qrtz_simple_triggers` ADD CONSTRAINT `qrtz_simple_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`); --- Limit table `qrtz_simprop_triggers`--ALTER TABLE `qrtz_simprop_triggers` ADD CONSTRAINT `qrtz_simprop_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`); --- Restriction table `qrtz_triggers`--ALTER TABLE `qrtz_triggers` ADD CONSTRAINT `qrtz_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `JOB_NAME`, `JOB_GROUP`) REFERENCES `qrtz_job_details` (`SCHED_NAME`, `JOB_NAME`, `JOB_GROUP`);<br><br><br></em>

The implementation principle of quartz cluster uses the database to record the job behavior, and through the lock mechanism, the job is run only once in the same time.

JobBean Example

 //It needs to be handed over to spring to manage @Service("dialogJob")public class DialogJob { @Autowired private QuestionService questionService;// The method name is defined in quartz public void execute() throws Exception{ //Specific execution of business questionService.XXXXX(); } }

Summarize

The above is the entire content of this article. I hope that the content of this article has certain reference value for everyone's study or work. If you have any questions, you can leave a message to communicate. Thank you for your support to Wulin.com.