Shulou(Shulou.com)06/02 Report--

This article focuses on "how to use the Beanstalkd queue". Interested friends may wish to have a look at it. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to use the Beanstalkd queue.

Installation

Official website: https://kr.github.io/beanstalkd/

Install (you can also install with composer)

Yum install beanstalkd-enablerepo=epel or composer require pda/pheanstalk

one

Start (0.0.0.0 can run any ip to connect)

/ usr/bin/beanstalkd-l 0.0.0.0-p 11300-b / var/lib/beanstalkd/binlog-F

-b enable binlog. Restart after a power outage will automatically resume the task.

one

Configuration file

/ etc/sysconfig/beanstalkd

one

Basic concept

Core concepts in Beanstalkd design:

Job: a task that needs to be processed asynchronously, is the basic unit in Beanstalkd, and needs to be placed in a tube.

Tube: a well-known task queue that stores uniform types of job and is the object of producer and consumer operations.

The producer of producer:Job, using the put command to put a job into a tube.

The consumer of consumer:Job uses the reserve/release/bury/delete command to get the job or change the state of the job.

Life cycle of job

When producer directly put a job, the job is in the READY state, waiting for the consumer to process. If you choose to delay the put,job, you will first go to the DELAYED state, and then migrate to the READY state after the waiting time.

After consumer acquires the job of the current READY, the state of the job is migrated to RESERVED, so that other consumer can no longer manipulate the job. When the consumer completes the job, you can choose the delete, release or bury operation; after delete, the job dies from the system and cannot be obtained again; the release operation can re-migrate the job state back to READY (or delay the state transition operation), so that other consumer can continue to obtain and execute the job What's interesting is the bury operation. You can hibernate the job, and then return the dormant job kick to READY state when needed, or job in delete BURIED state.

It is precisely with these interesting operations and states that many meaningful applications can be made based on this. For example, to implement a circular queue, you can hibernate the job in the RESERVED state, and then kick the job in the BURIED state back to the READY state when there is no job in the BURIED state.

READY-A task that needs to be processed immediately and automatically becomes the current task when the DELAYED task expires

DELAYED-A delayed task, which can be delayed by putting the message back into the DELAYED queue again after the consumer has processed the task

RESERVED-A task that has been acquired by the consumer and is being performed. Beanstalkd is responsible for checking whether the task is completed within TTR (time-to-run)

BURIED-reserved task: the task will not be executed and will not disappear unless someone kicks it back into the queue

DELETED-the message is completely deleted. Beanstalkd no longer maintains these messages.

Some characteristics

Priority

A task (job) can have 0-2 ^ 32 priorities, 0 represents the highest priority, and the default priority is 1024.

Persistence

Job and its status can be recorded in a file through binlog, and the previous job and state can be restored by reading binlog the next time Beanstalkd starts.

Distributed fault tolerance

Distributed design is similar to Memcached, beanstalkd server do not know the existence of each other, are distributed through client and go to a specific server to get job according to the tube name.

Timeout control

In order to prevent a consumer from occupying the task for a long time but cannot handle it, Beanstalkd sets the timeout time for the reserve operation. If the consumer cannot be completed within the specified time, the job,job will be migrated back to the READY state for other consumer to execute.

Client Libraries For PHP

Project address: https://github.com/pda/pheanstalk/

Producer example: add job to the queue

$pheanstalk = new Pheanstalk_Pheanstalk ('127.0.0.1'); $pheanstalk-> useTube ('tubeName')-> put ($jobData)

Consumer example: take a job from the queue

$job = $pheanstalk- > watch ('tubeName')-> ignore (' default')-> reserve (); echo $job- > getData (); $pheanstalk- > delete ($job)

Check service status

$isAlive = $pheanstalk- > getConnection ()-> isServiceListening (); / / return true or false4 to get the data of a tube try {$tubeStatus = $pheanstalk- > statsTube ('tubeName');} catch (Exception $e) {if ($e-> getMessage () = =' Server reported NOT_FOUND') {/ / tube does not exist $current_jobs_ready = 0;}} at this point, I believe you have a better understanding of "how to use Beanstalkd queue", so you might as well do it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.