Wrapper for Gearman so that you get command lines tools and can use annotation in Symfony.
Also supports the Symfony web profiling toolbar integration.
{
"require": {
"laelaps/symfony-gearman-bundle": "1.*@dev"
}
}
We can configure one server for the client. Because only one is used. You need load balancer if you would like to share the load over multiple Gearman servers.
We can configure multiple servers for the workers. Because they do look for work on all configured Gearman servers.
laelaps_gearman:
client_server: localhost:4730
worker_servers:
- localhost:4730
<?php
public function registerBundles()
{
$bundles = array(
// ...
new Laelaps\GearmanBundle\LaelapsGearmanBundle(),
// ...
);
}
There is a simple supervisor bash script available. For instructions, see:
<?php
// AcmeDemoBundle\Worker\ExampleWorker.php
namespace AcmeDemoBundle\Worker;
use GearmanJob;
use Laelaps\GearmanBundle\Annotation as Gearman;
use Laelaps\GearmanBundle\Worker;
use Symfony\Component\Console\Output\OutputInterface;
class ExampleWorker extends Worker
{
/**
* @Gearman\PointOfEntry(name="example_job_name")
* @param GearmanJob $job
* @param Symfony\Component\Console\Output\OutputInterface $output
* @return boolean returning false means job failure
*/
public function doExampleJob(GearmanJob $job, OutputInterface $output)
{
// do your job
}
}
Symfony Style Notation
$ ./app/console gearman:worker:run AcmeBundle:ExampleWorker
Note that this would look for Acme\Bundle\AcmeBundle\Worker\ExampleWorker
$ ./app/console gearman:worker:run ./src/AcmeDemoBundle/Worker/ExampleWorker.php
Wildcard is also available (not recommended but possible - results in single process for multiple workers):
$ ./app/console gearman:worker:run "./src/AcmeDemoBundle/Worker/*.php"
Runs all workers from all bundles:
$ ./app/console gearman:worker:run "./src/*/Worker/*.php"
<?php
class ExampleController
{
public function exampleAction()
{
// job name taken from PointOfEntry annotation
$this->get('laelaps.gearman.client')->doBackground('example_job_name', $optionalWorkload = '');
}
}
$ ./app/console gearman:job:run example_job_name
$ ./app/console gearman:job:run example_job_name optional_workload_string
As an alternative to the Worker implementation, there is a Consumer-Handler implementation.
place jobs on the queue with:
<?php
$gearman->doBackground('queueName', serialize($workload));
write a handler like:
<?php
namespace AcmeDemoBundle\Worker;
use Laelaps\GearmanBundle\Worker\HandlerInterface;
use Psr\Log\LoggerInterface;
class ConsumerHandler implements HandlerInterface
{
/** @var LoggerInterface */
protected $logger;
/**
* @param LoggerInterface $logger
*/
public function __construct(LoggerInterface $logger)
{
$this->logger = $logger;
}
/**
* {@inheritdoc}
*/
public function handle($message)
{
try {
$workload = unserialize($message);
echo $workload;
} catch (Exception $e) {
$this->logger->error(sprintf("%s: %s", static::class, $e->getMessage()));
return false;
}
return true;
}
}
And add this class to your service container with a tag:
acme.worker.consumer_handler:
class: AcmeDemoBundle\Worker\ConsumerHandler
arguments:
- "@logger"
tags:
- { name: laelaps.handler, queue_name: 'queueName'}
and run it with:
$ ./app/console gearman:consumer:queueName