Suddenly gearman workers start refusing jobs but works fine after restart. about net_gearman HOT 5 CLOSED

The first thing I would recommend is to change the config to use dedicated workers for the jobs that are not getting done. If dedicated workers still don't get them done, then something else may be going on.

from net_gearman.

Thanks for the reply. I have observed the same pattern of logs in the gearman-manager.log at the time of issue when processing gets stuck suddenly for some specific function on the worker server. Please suggest your views on this.

[2018-02-05 15:54:09.733015] 14702 PROC Started child 17607 (job1,job2,job3,job4,job5)
[2018-02-05 15:54:09.733114] 14702 DEBUG Registering signals for child
[2018-02-05 15:54:09.733408] 17607 DEBUG Adjusted max run time to 647 seconds (max_worker_lifetime:600 + splay:47)
[2018-02-05 15:54:09.733512] 17607 WORKER Adding server 127.0.0.1
[2018-02-05 15:54:09.733604] 17607 WORKER Adding job job1 ; timeout:
[2018-02-05 15:54:09.733665] 17607 WORKER Adding job job2 ; timeout:
[2018-02-05 15:54:09.733716] 17607 WORKER Adding job job3 ; timeout:
[2018-02-05 15:54:09.733765] 17607 WORKER Adding job job4 ; timeout:
[2018-02-05 15:54:09.733813] 17607 WORKER Adding job job5 ; timeout:
[2018-02-05 15:54:18.765310] 14702 PROC Child 17606 exited with error code of 0 (job1,job2,job3,job4,job5)

from net_gearman.

Does another worker not get started? What does your worker code look like?

from net_gearman.

This looks odd:

WORKER Adding job job2 ; timeout:

There is no timeout there. If there is not timeout, the logs don't add the timeout: label. e.g.

21468 WORKER Adding job Reverse_String

I am guessing something in your config is setting a bad timeout and perhaps there is some bug in the code that is treating that as zero. I can't replicate that with the config you showed above.

from net_gearman.

No new feedback

from net_gearman.