Gearman (Part 2): Create jobs, add workers, do work

Other posts in this series

• Gearman (Part 1): Setup Gearmand
• Gearman (Part 2): Create jobs, add workers, do work
• Gearman (Part 3): More jobs, other stuff, a better title (soon after Part 2)

Now that Gearmand is setup we need to get some workers going. Gearman is itself language agnostic; it doesn’t really care if your client/worker is in Python, PHP or Ruby, to name a few. There are several libraries available to help you get going.

##PECL::Gearman In order to get clients and workers setup using PHP you need to have libgearman installed; this came with Gearmand from my previous post in this series. For this example I’ll be using the Gearman PECL extension. I assume you already have PHP installed on your system.

By default, the configure script looks in

1

/usr/local

1

/usr

1

/opt/local

To install using PECL, run

~$ (sudo) pecl install gearman-beta

The

1

-beta

Side Note: This should work fine for installations of libgearman I covered previously, but if you’re like myself and have your Homebrew installed elsewhere (I use Cinderella), your header files are in a different place, and you’ll need to compile the extension by downloading the source, extracting it, and running the following

1
2
3
4
5
6
7
~$ cd Downloads/gearman-0.7.0/gearman-0.7.0
~$ phpize
~$ ./configure --with-gearman=`brew --prefix`
~$ make
~$ (sudo) make install
Installing shared extensions:     /usr/lib/php/extensions/no-debug-non-zts-20090626/
~$

When the installation completes, you should receive instructions on activating the extension. They typically involve updating your

1

php.ini

1

extension_dir

1

extension=gearman.so

To confirm everything is OK, create a simple php file that echo’s out the gearman version:

//gearman_version.php
<?php
echo "Gearman version: " . gearman_version() . PHP_EOL;
?>

And run the file

~$ php gearman_version.php
Gearman version: 0.15

##Creating Jobs

• Jobs are created by Clients, who send them to the Gearman server via Tasks
• A Task is communication about a job, such as “run this job” or “what is the status of this job”
• A Job is something the worker does
• Workers continuously waiting on the job server to tell them when to start and with what arguments
• Clients submit jobs and ask for status about jobs (both of those things are considered tasks)
• Workers actually perform the jobs

Source here

We’ll start with a very simple “reverse string” job to get going. First we’ll create the client to submit the job. We do so by instantiating a new

1

GearmanClient

1

do

//  reverse_do.php
<?php
# Create our client object.
$client= new GearmanClient();

# Add default server (localhost).
$client->addServer('localhost','4730');

echo "Sending job...\n";
# Send reverse job

$result = $client->do("reverse", "Hello World!");

echo "Result: {$result}" . PHP_EOL;
?>

You can run this on the command line like so:

~$ php reverse_do.php 
Sending job...

The client will wait for the response (there are other types of jobs where the client does not wait, called background jobs).

Now we create a worker in a similar process: instantiating a new

1

GearmanWorker

//  reverse_worker.php
<?php

$worker = new GearmanWorker();
$worker->addServer('localhost','4730');
$worker->addFunction('reverse', 'reverse_function');

while ($worker->work());

function reverse_function($job)
{
    //  For example purpose
    echo "Received job: {$job->handle()}" . PHP_EOL; 
    return strrev($job->workload());
}
?>

Now we run the worker from another terminal session. Because we’ve put the worker in an endless

1

while

1

cntrl+c

~$ php reverse_worker.php 
Received job: H:Waffles.local:11

Back on the original terminal session, where we left the client waiting, you should see an update:

~$ php reverse_do.php 
Sending job...
Result: !dlroW olleH
~$ 

The Gearmand server held on to the job until a worker arrived that could preform the work. Once our worker fired up, the server handed the job over, the worker did the work, and told the server it was done and could accept more work. The server in turn passed the result back to the client, and the client process terminated, printing the reversed string.

@ctshryock

• About
• Archive 
• Projects
• Web Errors 
• Github➚
• Twitter➚