定时任务系列(9)-Quartz启动核心原理之错过调度

再回到上一章的的开头,我们分析了集群的地方也还有一段代码:

       misfireHandler = new MisfireHandler();
        if(initializersLoader != null)
            misfireHandler.setContextClassLoader(initializersLoader);
        misfireHandler.initialize();
        schedulerRunning = true;

这一段就是初始化一个MisfireHandler线程,MisfireHandler也是JobStoreSupport的一个内部类,同集群的初始化方法一样,这里的初始化方法也执行了线程的执行。
直接看run方法

     while (!shutdown) {

         long sTime = System.currentTimeMillis();
         //获取misfired的job
         RecoverMisfiredJobsResult recoverMisfiredJobsResult = manage();

         if (recoverMisfiredJobsResult.getProcessedMisfiredTriggerCount() > 0) {
             signalSchedulingChangeImmediately(recoverMisfiredJobsResult.getEarliestNewTime());
         }

         if (!shutdown) {
             long timeToSleep = 50l;  // At least a short pause to help balance threads
             if (!recoverMisfiredJobsResult.hasMoreMisfiredTriggers()) {
                 timeToSleep = getMisfireThreshold() - (System.currentTimeMillis() - sTime);
                 if (timeToSleep <= 0) {
                     timeToSleep = 50l;
                 }

                 if(numFails > 0) {
                     timeToSleep = Math.max(getDbRetryInterval(), timeToSleep);
                 }
             }

             try {
                 Thread.sleep(timeToSleep);
             } catch (Exception ignore) {
             }
         }//while !shutdown
     }
 }

首先获取misfired的job,根据不同策略设定的调度时间,重新调度任务
例如:

  • MISFIRE_INSTRUCTION_FIRE_ONCE_NOW:立即执行一次
  • MISFIRE_INSTRUCTION_DO_NOTHING:等待下一次触发
  • MISFIRE_INSTRUCTION_IGNORE_MISFIRE_POLICY:忽略异常

然后再每个间隔(默认50ms)重新检测misfired

现在来看看quartz如何获取misfired的job,直接看manage方法中的doRecoverMisfires方法

    protected RecoverMisfiredJobsResult doRecoverMisfires() throws JobPersistenceException {
        boolean transOwner = false;
        Connection conn = getNonManagedTXConnection();
        try {
            RecoverMisfiredJobsResult result = RecoverMisfiredJobsResult.NO_OP;
            
            // Before we make the potentially expensive call to acquire the 
            // trigger lock, peek ahead to see if it is likely we would find
            // misfired triggers requiring recovery.
            // 在我们进行潜在的昂贵调用以获取触发器锁之前,请提前查看是否可能会发现需要恢复的未触发触发器。
            // 这里如果没有失火的话,是可以不用拿锁的
            int misfireCount = (getDoubleCheckLockMisfireHandler()) ?
                getDelegate().countMisfiredTriggersInState(
                    conn, STATE_WAITING, getMisfireTime()) : 
                Integer.MAX_VALUE;
            
            if (misfireCount == 0) {
                getLog().debug(
                    "Found 0 triggers that missed their scheduled fire-time.");
            } else {
                transOwner = getLockHandler().obtainLock(conn, LOCK_TRIGGER_ACCESS);
                //拿到锁后处理失火故障
                result = recoverMisfiredJobs(conn, false);
            }
            
            commitConnection(conn);
            return result;
        } catch (JobPersistenceException e) {
            rollbackConnection(conn);
            throw e;
        } catch (SQLException e) {
            rollbackConnection(conn);
            throw new JobPersistenceException("Database error recovering from misfires.", e);
        } catch (RuntimeException e) {
            rollbackConnection(conn);
            throw new JobPersistenceException("Unexpected runtime exception: "
                    + e.getMessage(), e);
        } finally {
            try {
                releaseLock(LOCK_TRIGGER_ACCESS, transOwner);
            } finally {
                cleanupConnection(conn);
            }
        }
    }

这里在获取锁前再查询一次是否有失火的任务,获取锁的开销是很大的,这里的处理尽量避免获取锁。拿到锁后处理失火故障:

    protected RecoverMisfiredJobsResult recoverMisfiredJobs(
        Connection conn, boolean recovering)
        throws JobPersistenceException, SQLException {

        // If recovering, we want to handle all of the misfired
        // triggers right away.
        int maxMisfiresToHandleAtATime = 
            (recovering) ? -1 : getMaxMisfiresToHandleAtATime();
        
        List<TriggerKey> misfiredTriggers = new LinkedList<TriggerKey>();
        long earliestNewTime = Long.MAX_VALUE;
        // We must still look for the MISFIRED state in case triggers were left 
        // in this state when upgrading to this version that does not support it.
        //我们仍然必须寻找 MISFIRED 状态,以防在升级到不支持它的版本时触发器处于此状态。
        //SELECT TRIGGER_NAME, TRIGGER_GROUP FROM t_rb_qrtz_TRIGGERS WHERE SCHED_NAME = 'scheduler'
        // AND NOT (MISFIRE_INSTR = -1) AND NEXT_FIRE_TIME < '1662464980466' AND TRIGGER_STATE = 'WAITING' ORDER BY NEXT_FIRE_TIME ASC, PRIORITY DESC
        boolean hasMoreMisfiredTriggers =
            getDelegate().hasMisfiredTriggersInState(
                conn, STATE_WAITING, getMisfireTime(), 
                maxMisfiresToHandleAtATime, misfiredTriggers);

        if (hasMoreMisfiredTriggers) {
            getLog().info(
                "Handling the first " + misfiredTriggers.size() +
                " triggers that missed their scheduled fire-time.  " +
                "More misfired triggers remain to be processed.");
        } else if (misfiredTriggers.size() > 0) { 
            getLog().info(
                "Handling " + misfiredTriggers.size() + 
                " trigger(s) that missed their scheduled fire-time.");
        } else {
            getLog().debug(
                "Found 0 triggers that missed their scheduled fire-time.");
            return RecoverMisfiredJobsResult.NO_OP; 
        }

        for (TriggerKey triggerKey: misfiredTriggers) {
            
            OperableTrigger trig = 
                retrieveTrigger(conn, triggerKey);

            if (trig == null) {
                continue;
            }
            //真正更新失火的数据
            doUpdateOfMisfiredTrigger(conn, trig, false, STATE_WAITING, recovering);

            if(trig.getNextFireTime() != null && trig.getNextFireTime().getTime() < earliestNewTime)
                earliestNewTime = trig.getNextFireTime().getTime();
        }

前面再次查询一次处于WAITING状态的trigger,拿到所有失火的数据再找到trigger,将trigger封住成OperableTrigger,再针对每个Trigger更新下次调度时间。

    private void doUpdateOfMisfiredTrigger(Connection conn, OperableTrigger trig, boolean forceState, String newStateIfNotComplete, boolean recovering) throws JobPersistenceException {
        Calendar cal = null;
        if (trig.getCalendarName() != null) {
            cal = retrieveCalendar(conn, trig.getCalendarName());
        }

        schedSignaler.notifyTriggerListenersMisfired(trig);
        //失火处理策略的更新
        trig.updateAfterMisfire(cal);

        if (trig.getNextFireTime() == null) {
            storeTrigger(conn, trig,
                null, true, STATE_COMPLETE, forceState, recovering);
            schedSignaler.notifySchedulerListenersFinalized(trig);
        } else {
            storeTrigger(conn, trig, null, true, newStateIfNotComplete,
                    forceState, recovering);
        }
    }

先通知所有的监听失火的监听器,然后修改具体的trigger,再重新将trigger写入数据库。

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
动态定时任务调度可以使用Spring Boot、Vue和Quartz来实现。下面是一个基本的实现步骤: 1. 在Spring Boot中配置Quartz 在pom.xml文件中添加Quartz依赖: ```xml <dependency> <groupId>org.quartz-scheduler</groupId> <artifactId>quartz</artifactId> <version>2.3.0</version> </dependency> ``` 在application.yml文件中添加Quartz的配置: ```yaml spring: quartz: job-store-type: jdbc jdbc: initialize-schema: always comment-prefix: QRTZ_ scheduler-name: MyScheduler properties: org: quartz: jobStore: driverDelegateClass: org.quartz.impl.jdbcjobstore.PostgreSQLDelegate useProperties: true threadPool: threadCount: 3 plugin: shutdownhook: class: org.quartz.plugins.management.ShutdownHookPlugin jobInitializer: class: org.quartz.plugins.xml.XMLSchedulingDataProcessorPlugin filePath: quartz/jobs.xml ``` 2. 创建Job类 创建一个继承自Quartz的Job类,并实现execute方法。这个方法中就是我们要执行定时任务。 ```java public class MyJob implements Job { @Override public void execute(JobExecutionContext context) throws JobExecutionException { //TODO: 执行定时任务的代码 } } ``` 3. 创建Trigger类 创建一个Trigger类,用于定义定时任务调度规则。例如每天的凌晨1点执行一次任务。 ```java public class MyTrigger { public static Trigger getTrigger() { return TriggerBuilder.newTrigger() .withIdentity("MyTrigger", "MyGroup") .withSchedule(CronScheduleBuilder.cronSchedule("0 0 1 * * ? *")) .build(); } } ``` 4. 创建JobDetail类 创建一个JobDetail类,用于定义要执行的任务。 ```java public class MyJobDetail { public static JobDetail getJobDetail() { return JobBuilder.newJob(MyJob.class) .withIdentity("MyJob", "MyGroup") .storeDurably() .build(); } } ``` 5. 添加任务到Quartz中 创建一个SchedulerFactoryBean,用于将任务添加到Quartz中。 ```java @Configuration public class QuartzConfig { @Autowired private ApplicationContext applicationContext; @Bean public SchedulerFactoryBean schedulerFactoryBean() throws IOException { SchedulerFactoryBean schedulerFactoryBean = new SchedulerFactoryBean(); schedulerFactoryBean.setOverwriteExistingJobs(true); schedulerFactoryBean.setSchedulerName("MyScheduler"); schedulerFactoryBean.setAutoStartup(true); schedulerFactoryBean.setApplicationContext(applicationContext); Properties quartzProperties = new Properties(); quartzProperties.load(new ClassPathResource("quartz.properties").getInputStream()); schedulerFactoryBean.setQuartzProperties(quartzProperties); List<Trigger> triggers = new ArrayList<>(); triggers.add(MyTrigger.getTrigger()); Map<JobDetail, List<Trigger>> jobDetails = new HashMap<>(); jobDetails.put(MyJobDetail.getJobDetail(), triggers); schedulerFactoryBean.setJobDetails(jobDetails); return schedulerFactoryBean; } } ``` 6. 创建Vue前端界面 在Vue中创建一个前端界面,用于动态添加、修改和删除定时任务。界面中需要包含定时任务的名称、调度规则和执行方法。 7. 实现动态添加、修改和删除定时任务 在Vue中,可以使用axios来发送HTTP请求,将任务信息发送到Spring Boot后端。在后端中,可以通过Quartz来动态添加、修改和删除定时任务。 8. 测试 启动Spring Boot应用程序,并访问Vue前端界面。添加一个定时任务,并查看任务是否按照调度规则执行

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值