Home  >  Article  >  Backend Development  >  About the implementation principle of Laravel queue and how to solve the problem

About the implementation principle of Laravel queue and how to solve the problem

不言
不言Original
2018-06-13 11:45:522386browse

This article mainly introduces a brief discussion of Laravel queue implementation principles and problem solving records. The content is quite good. I will share it with you now and give it as a reference.

Problem

The two projects developed by the company using Laravel are deployed on the same test server and share the same redis. When using queues in laravel, conflicts occur.

Find the cause of the problem

You can see pushRaw() in the operation class of laravel queue Illuminate\Queue\RedisQueue.php Method:

// 将一任务推入队列中
public function pushRaw($payload, $queue = null, array $options = [])
  {
    $this->getConnection()->rpush($this->getQueue($queue), $payload);

    return Arr::get(json_decode($payload, true), 'id');
  }

It can be seen from this method that the redis implementation of Lrarvel queue is implemented through the list structure, rpush(key, value) is to push value into the redis queue whose key value is key. The value of key is obtained through $this->getQueue($queue)

protected function getQueue($queue)
  {
    return 'queues:'.($queue ?: $this->default);
  }

So the key in the list in redis is 'queues:'.($queue ?: $this->default); spliced, $this->default The value is RedisQueue Loaded from the config\queue.php configuration during instantiation 'queue' => ' default', $queue is $this->dispatch( new jobClass()->onQueue($queue) ) when adding a queue.

// config\queue.php 文件中的redis配置部分
'redis' => [
      'driver'   => 'redis',
      'connection' => 'default',
      'queue'   => 'default',
      'expire'   => 60,
    ],

At this point, the cause of the queue conflict between the two projects has been found. Because 'queue' => 'default' in the redis queue configuration uses the default default, when sharing redis, the default queue list is all 'queue:default', which leads to conflicts.

Because the queue name monitored by queue monitoring is determined by the --queue parameter. If it is not passed, it will be the default value we set above. If it is passed, it will be processed in order from front to back according to the incoming queue name. , see the code Illuminate\Queue\Worker.php for details:

protected function getNextJob($connection, $queue)
  {
    if (is_null($queue)) {
      return $connection->pop();
    }

    foreach (explode(',', $queue) as $queue) {
      if (! is_null($job = $connection->pop($queue))) {
        return $job;
      }
    }
  }

$queue is the --queue= parameter passed in, When $queue does not exist, call $connection->pop() directly When the parameter exists, the parameter will be parsed, the queue name in front will be processed first, and the queue name will be passed into pop( $queue), pop()will try to get the queue task from the specified queue or the default queue

// Illuminate\Queue\RedisQueue.php
public function pop($queue = null)
  {
    $original = $queue ?: $this->default;

    $queue = $this->getQueue($queue);

    if (! is_null($this->expire)) {
      $this->migrateAllExpiredJobs($queue);
    }

    $job = $this->getConnection()->lpop($queue);

    if (! is_null($job)) {
      $this->getConnection()->zadd($queue.':reserved', $this->getTime() + $this->expire, $job);

      return new RedisJob($this->container, $this, $job, $original);
    }
  }

Now we understand the principle of queue execution.

Solution

Modify the default queue in the queue configuration file to a different name, such as: 'queue' => laravel1','queue' => ; laravel2'.

Queue listening php artisan queue:listen redis --queue=laravel1,syncExpress

Finally

encountered a problem, Don't rush to the doctor when you are sick. Start with the code, analyze and understand the implementation principles, and find the right point. The solution may be simple.

The above is the entire content of this article. I hope it will be helpful to everyone's study. For more related content, please pay attention to the PHP Chinese website!

Related recommendations:

Analysis on the method of using message queue queue and asynchronous queue in PHP's Laravel framework

The above is the detailed content of About the implementation principle of Laravel queue and how to solve the problem. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn