-
Notifications
You must be signed in to change notification settings - Fork 0
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 settings #28
Comments
It is a configuration in the "Default Node Executor" tab when you "Edit Configuration..." under "Project Settings" |
Also accessible in the text config as project.rancher-node-executor-timeout=36000 |
Thank you to save my time :-). |
Since it closes automatically as soon as the remote job is done, the timeout is really just a safety against DOSing ourselves. You really could make it large and not worry. I don't really think it's worth the extra code or extra settings you're need to think about on every job creation. It would be a low priority in any case. |
Hi, the timeout could be a clue as well for a job to know if every thing went "normaly" and when you have jobs that last few minutes for certains and few hours for the others on a same project, it's not easy to set an appropriate timeout :-/ |
I see your point about using duration to determine if a job is healthy -- but in most cases if I time it out, I risk leaving something broken. I think you would be much better off using a configuring a notification when average duration is exceeded. And since there is a purpose built tool for this in RunDeck notifications, I think that is a better choice. When some jobs take seconds and others take hours, it is fine to take the longer time -- I have a project where the timeout is 10 hours. I will keep this as a possible feature request, but it still seems like a very low priority. |
Hi,
I read that timeout for job execution could be set, but I did'nt find how.
Is this features available as a job "option" or as a config option ?
Thank you.
Regards
The text was updated successfully, but these errors were encountered: