-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
worker available is lost after a while #9
Comments
Does it occur with the currently nightly as well? |
I tried version |
anything in the worker log? |
the worker logs look normal to me. i can provide you a log per PM if you want. As far as I understand the worker creates his i think the main problem is that under some circumstances the "Worker Available" in the From the mod-gearman docs https://github.com/sni/mod_gearman#how-to i learned to use |
i can now reproduce the Problem. If i use the |
sounds reasonable. Thanks for the heads up. So is there anything from the worker side we could do? As far as i remember, the "old" worker renews the status worker from time to time which probably prevents this issue from happening. |
What is happening to me on CentOS8 is that mod_gearman go will do a denial of service on gearmand, with connections building up till it reaches 1000 open TCP connections and gearmand will not accept connections anymore. C Version Go Version - keeps going UP Tks. |
i guess that's something else. Do the worker have a reasonable limit of connections/threads ( |
No problem, will do it now, the conf is like this: job_timeout=60 `[2021-06-21 15:40:19.095][Error][mod_gearman_worker_linux.go:29] requested thread dump via signal user defined signal 1 goroutine 1 [select]: goroutine 19 [chan receive]: goroutine 8 [syscall]: goroutine 36 [sleep]: goroutine 20 [IO wait]: goroutine 21 [chan receive]: goroutine 50 [IO wait]: goroutine 51 [chan receive]: goroutine 52 [IO wait]: goroutine 53 [chan receive]: goroutine 54 [IO wait]: goroutine 55 [chan receive]: goroutine 66 [IO wait]: goroutine 67 [chan receive]: goroutine 68 [IO wait]: goroutine 69 [chan receive]: |
we are using mod-gearman-worker-go with OMD 2.90 (also with 3.00).
With the command
check_gearman -H localhost:4730 -q worker_<hostname> -x
we check the worker queues. Some workers lose the connection to their worker queue after some time.#6 did not help in this case.
When we restart the gearman_worker, it immediately reconnects.
The normal services queues are working as expected
The text was updated successfully, but these errors were encountered: