-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Minor improvements to single-worker-timeout support #2667
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
Conversation
Adjustments on top of PR spotify#1860 - Update documentation to clarify that worker-timeout configuration is supported for single workers - Add test to ensure/prove timeout feature works without setting the num-workers setting - Currently, for single-worker setups, the error message related to timeout is missing the actual timeout seconds in the error message. These changes improve the error message such that the logs properly display the timeout
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Much thanks for updating documentation and adding test to prove it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Nice PR! Did you check that the logging still looks okay for multiple workers?
@Tarrasch This is an excellent question and I should have included this in the PR.
and running with multiple workers:
|
Thanks for your contribution!! |
Description
PR #1860 by @daveFNbuck gives us support for
worker-timeout
supportin single-worker configuration.
Motivation and Context
worker-timeout
settingonly applies when using multiple workers. This is no longer true
after PR Enables worker timeouts with only one worker #1860. This PR updates the documentation to clarify.
multiple workers
related to timeout is missing the actual timeout seconds
in the error message.
The issue is
None seconds
is invalid. The PR addresses that issueby ensuring worker_timeout is a property of TaskProcess.
Have you tested this? If so, how?
I have tested this on my own workflows in python 2/3 environments.
Also I've locally executed the tests as outlined in the contributing guideline.