laravel queue timeout和retry_after配置的区别

cominglately

已于 2023-07-17 17:04:08 修改

阅读量580

点赞数

文章标签： laravel java 前端

于 2023-07-17 17:02:34 首次发布

本文链接：https://blog.csdn.net/cominglately/article/details/131770064

版权

文章详细解释了在Laravel中，retry_after配置用于指定任务在多长时间后重新入队，而timeout则是worker执行单个任务的最大时间限制。当任务超过retry_after时间未完成，将被重新加入队列；如果worker处理任务超过timeout时间，任务则会被终止。文章还展示了如何使用LUA脚本来迁移过期的延迟任务。

摘要由CSDN通过智能技术生成

文章目录

- - 场景
  - 解答

场景

retry_after是可以在配置文件中配置, timeout是queue:work的选项，两者之间的区别是什么

解答

生效的维度不同

retry_after 任务到retry_after秒仍未执行结束，那这个任务会重新入队
timeout 是worker进行执行单个任务的最大时间

–timeout[=TIMEOUT] The number of seconds a child process can run [default: “60”]

    protected function migrate($queue)
    {
        $this->migrateExpiredJobs($queue.':delayed', $queue);

        if (! is_null($this->retryAfter)) {
            $this->migrateExpiredJobs($queue.':reserved', $queue);
        }
    }
    /**
     * Migrate the delayed jobs that are ready to the regular queue.
     *
     * @param  string  $from
     * @param  string  $to
     * @return array
     */
    public function migrateExpiredJobs($from, $to)
    {
        return $this->getConnection()->eval(
            LuaScripts::migrateExpiredJobs(), 3, $from, $to, $to.':notify', $this->currentTime()
        );
    }
    /**
     * Get the Lua script to migrate expired jobs back onto the queue.
     *
     * KEYS[1] - The queue we are removing jobs from, for example: queues:foo:reserved
     * KEYS[2] - The queue we are moving jobs to, for example: queues:foo
     * KEYS[3] - The notification list for the queue we are moving jobs to, for example queues:foo:notify
     * ARGV[1] - The current UNIX timestamp
     *
     * @return string
     */
    public static function migrateExpiredJobs()
    {
        return <<<'LUA'
-- Get all of the jobs with an expired "score"...
local val = redis.call('zrangebyscore', KEYS[1], '-inf', ARGV[1])

-- If we have values in the array, we will remove them from the first queue
-- and add them onto the destination queue in chunks of 100, which moves
-- all of the appropriate jobs onto the destination queue very safely.
if(next(val) ~= nil) then
    redis.call('zremrangebyrank', KEYS[1], 0, #val - 1)

    for i = 1, #val, 100 do
        redis.call('rpush', KEYS[2], unpack(val, i, math.min(i+99, #val)))
        -- Push a notification for every job that was migrated...
        for j = i, math.min(i+99, #val) do
            redis.call('rpush', KEYS[3], 1)
        end
    end
end

return val
LUA;
    }
    ```