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
"timeout" setting used for two things that should be distinct #1658
Comments
I can't find a reference right now, but I'll look more later. We have discussed this in other issues before, for sure. I mostly agree. I'm not sure there needs to be a difference between the startup timeout and the worker timeout, but I do think a separate request timeout would be helpful especially because the current timeout functions as a request timeout for the sync worker (but not for the others). |
@benoitc @berkerpeksag should we add a request timeout setting to distinguish it from the worker heartbeat timeout? |
It looks like a proper request timeout feature will require separate implementations for each worker class. A narrower feature, along the lines of @tilgovi et. al., might you be receptive to such an approach? |
There's a commit (the more recent one) demonstrating such an initialization-time delay. I used a slightly less obscure config setting name, |
@tilgovi any update on this? A request timeout for async worker would be a great feature |
@opiumozor nope! I'm happy to review PRs and discuss implementation if you want to take it on, though! |
Proposed as a solution for issue benoitc#1658
Proposed as a solution for issue benoitc#1658
Proposed as a solution for issue benoitc#1658
Proposed as a solution for issue benoitc#1658
Proposed as a solution for issue benoitc#1658
Proposed as a solution for issue benoitc#1658
A new timeout-start-after value is added to config, granting workers an initial grace period to do time-consuming initialization, after which they are held to timeout stricture. Previous attempts of mine to form an acceptable pull request have failed linting in CI, all in code I didn't touch. This branch is newly minted from the current upstream master.
Workers are killed if they have not responded within
timeout
seconds. However, when a worker is spawned it is also killed if it doesn't finish spawning withintimeout
seconds. In my opinion these two timeout values should be configured independently. I have a worker which takes a long time to spawn (over 30s) but it should handle requests quickly. I would like thetimeout
setting set to a small value (say30
) and a newspawn_timeout
set to a large value (say60
).Would this be a good idea? What do others think?
The text was updated successfully, but these errors were encountered: