Set timeout on each job
Hello, is there anyway to set a hard limit timeout for each job? Thank you!
7 Replies
Solution
Hey @justin it seems like if there's an exception thrown before
runpod.serverless.start is called, the timeout above will not work, and my worker is stuck in that state for a very long time... 😦hm unfortunately im not sure why ur worker would get caught in an exception thrown state usually that just crashes the app and exits. Id say try catch ur code if that is an issue so it always returns then?
u can kill ur worker manually too if needed
yes, that means i have to constantly monitor the run status. It would be nice if the timeout also apply to the entire bring up worker process too.
Is there anyway to submit this feature request to the RunPod Team?
Its impossible to apply to the entire worker process because serverless only kicks in once you actually call
runpod.serverless.start().
You should determine what is causing the exceptions before runpod.serverless.start() is called, and fix it.Thank you! Is the best practice to call runpod.serverless.start(). then load the model in memory?
No, best to load the model before calling it.