Closed p-alik closed 6 years ago
We have seen a similar problem in which the worker does not fetch jobs from either of our two configured gearmand servers, despite many outstanding jobs existing. The worker goes into a loop calling select,
getpeername(3, {sa_family=AF_INET, sin_port=htons(4730), sin_addr=inet_addr("1.2.3.4")}, [16]) = 0 getpeername(4, {sa_family=AF_INET, sin_port=htons(4730), sin_addr=inet_addr("5.6.7.8.9")}, [16]) = 0 select(8, [3 4], NULL, NULL, {11, 829717}) = 0 (Timeout)
(IP addresses changed.) According to "workers" on the gearmand server, no functions are registered for our worker.
Hope this helps.
Dave
thanks, @davel
@davel, I can't reproduce the issue. It doesn't appear anymore. Is it an issue with particular gearmand
version?
We are running gearmand 1.0.6 under Ubuntu 14.04 in round-robin mode.
thanks, @davel.
Maybe try upgrading to gearmand 1.1.17, @davel ?
simple client/worker implementation:
worker runs endless. After a while worker does not work on some of the job servers.