GRAB_ALL undocumented and not supported by older versions of server

Bug #923463 reported by Joern Heissler on 2012-01-29
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gearman
Low
Brian Aker

Bug Description

Neither the example "reverse" worker nor my own worker were able to connect to my gearman server.
I found out that a GEARMAN_COMMAND_GRAB_JOB_ALL is sent and the server then closes the connection. The server is probably a bit outdated.

gearman_worker_remove_options(worker, GEARMAN_WORKER_GRAB_ALL); apparantly fixes the problem.

There seems to be no documentation at all for GEARMAN_COMMAND_GRAB_JOB_ALL and GEARMAN_WORKER_GRAB_ALL.

I think that the default options should be changed for compatibility. Or at least that behaviour should be documented.

Related branches

Hi,

Are you asking about using an older server with a more modern worker?

Cheers,
 -Brian

On Jan 29, 2012, at 11:34 AM, Joern Heissler wrote:

> Public bug reported:
>
> Neither the example "reverse" worker nor my own worker were able to connect to my gearman server.
> I found out that a GEARMAN_COMMAND_GRAB_JOB_ALL is sent and the server then closes the connection. The server is probably a bit outdated.
>
> gearman_worker_remove_options(worker, GEARMAN_WORKER_GRAB_ALL);
> apparantly fixes the problem.
>
> There seems to be no documentation at all for
> GEARMAN_COMMAND_GRAB_JOB_ALL and GEARMAN_WORKER_GRAB_ALL.
>
> I think that the default options should be changed for compatibility. Or
> at least that behaviour should be documented.
>
> ** Affects: gearmand
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> Gearman.
> https://bugs.launchpad.net/bugs/923463
>
> Title:
> GRAB_ALL undocumented and not supported by server
>
> Status in Gearman Server and Client Libraries:
> New
>
> Bug description:
> Neither the example "reverse" worker nor my own worker were able to connect to my gearman server.
> I found out that a GEARMAN_COMMAND_GRAB_JOB_ALL is sent and the server then closes the connection. The server is probably a bit outdated.
>
> gearman_worker_remove_options(worker, GEARMAN_WORKER_GRAB_ALL);
> apparantly fixes the problem.
>
> There seems to be no documentation at all for
> GEARMAN_COMMAND_GRAB_JOB_ALL and GEARMAN_WORKER_GRAB_ALL.
>
> I think that the default options should be changed for compatibility.
> Or at least that behaviour should be documented.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gearmand/+bug/923463/+subscriptions

Brian Aker (brianaker) on 2012-01-30
Changed in gearmand:
status: New → Incomplete

Hi,

> Are you asking about using an older server with a more modern worker?

That's what I'm doing; server reports "gearmand 0.14 - https://launchpad.net/gearmand", worker is 0.27

But my question / request is more about adding documentation for the GRAB_ALL feature as it breaks compatibility.

Cheers
Joern

Brian Aker (brianaker) on 2012-05-24
Changed in gearmand:
importance: Undecided → Low
assignee: nobody → Brian Aker (brianaker)
status: Incomplete → Confirmed
Brian Aker (brianaker) on 2012-11-01
summary: - GRAB_ALL undocumented and not supported by server
+ GRAB_ALL undocumented and not supported by older versions of server
Clint Byrum (clint-fewbar) wrote :

------------------------------------------------------------
revno: 440.1.8
committer: Brian Aker <email address hidden>
branch nick: gearmand-trunk
timestamp: Tue 2011-06-28 18:54:24 -0700
message:
  1) Update tests so that we have a single notion of port.
  2) Fix a number of issues related to old style functions calling partition.

The commit above made libgearman incompatible with any job server that doesn't implement JOB_GRAB_ALL.

Clint Byrum (clint-fewbar) wrote :
Changed in gearmand:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers