Jobs execute in order of functions added, then priority

[Doug Harple]

When determining which job to run next, it appears that the worker does the following:

1) Iterates over functions in the order in which they were added.
2) For each function, it pulls the highest priority available job, in the order that the job was added.

This behavior confused me at first, and led me to believe that the prioritization system was broken.

The behavior I expected was that it would pull the highest priority job from the set of functions added to the worker.

(If this is working as designed, that's OK, I can work around it. I couldn't find anything in the documentation regarding the behavior.)

[Doug Harple (dharple)]

For example, I have a single worker that listens for functions a() and b():

$worker = new GermanWorker();
$worker->addServer();
$worker->addFunction('a', 'a');
$worker->addFunction('b', 'b');
while ($worker->work());

I stop the worker, and I then run a client that does the following:

$client = new GearmanClient();
$client->addServer();
$client->doHighBackground('b', 'whatever');
$client->doLowBackground('a', 'whatever');

If I then start the worker, it will run the low priority task before the high priority task, due to the order in which the functions were added to the worker.

[Brian Aker (brianaker)]

I need to dig through the code. This was switched at one point and I can no longer remember why.

[Clint Byrum (clint-fewbar)]

I added the --round-robin option a while back, but we had round robin mode off by default because of your concerns that people might be expecting the (rather insidious) "drain the last one registered completely" behavior.