Failed to return job results
My serverless endpoint is timing out after the client configured timeout of 30 seconds, even though the request is processed in under 10 seconds. I am using the python client (runpod==1.4.2). This is happening only on non-active workers. Below is one sample request from logs. I have submitted more details in the support request 3922
Solution:Jump to solution
this is solved.
I incorrectly assumed from the docs that TTL means max delayTime to set but looks like it means delayTime + executionTime....
9 Replies
Solution
this is solved.
I incorrectly assumed from the docs that TTL means max delayTime to set but looks like it means delayTime + executionTime.
TTL is how long to keep the job in the queue before it auto deletes, there shouldn't really be a reason to change the default unless you have regulatory concerns.
So according to the docs your assumption is correct, but maybe the docs are wrong if you found it to be incorrect in practice.
Send a request | RunPod Documentation
The method in which jobs are submitted and returned.
"TTL (Time-to-Live): Defines the maximum time a job can remain in the queue before it's automatically terminated. This parameter ensures that jobs don't stay in the queue indefinitely."
yea, i thought once the job is being executed, it's no longer in the "queue".
Yeah, maybe @PatrickR needs to fix the docs if they are wrong.
in architectures where there is a message broker and workers picking up jobs from queues, sometimes a "TTL" is configured to define a "max age" of the job in the queue, i thought this is similar
Based on your experience, it seems that TTL includes both the delay time and the execution time, rather than just the maximum time a job can spend in the queue before execution. Could you please confirm if this understanding is correct?
Yes, that’s my understanding.