Comment 6 for bug 609300

Yeah, the Gearman Job Server will re-submit any job that was running on
worker that has lost connectivity with the server, so this is expected
behavior (well, the re-submission is expected). But the problem here is
that sense the java worker will always crash when running that job, as
you point out, it results in all your workers going down.

Until this gets fixed, one possible workaround would be to have the
worker store the string somewhere where it can be retrieved and then
have the worker return to a URL/path to where the string can be picked
up. This is the generally accepted practice for workers that generate
large results sets, although I would be hard pressed to call 150K a
large result set.

Wilton Risenhoover wrote:
> The other problem, I'm finding out, is that as each worker dies, gearman
> (correctly) dishes the job out to another worker, which also
> subsequently dies. This produces a cascading effect leaving me with
> zero workers at the end.
>
> Any thoughts?
>
>