Augenbrauensenker
RRunPod
•Created by Augenbrauensenker on 11/20/2024 in #⚡｜serverless
Runpod requests fail with 500
also when i try to open my endpoint in UI, it redirects to 404.
I didn't change anything.
6 replies
RRunPod
•Created by Augenbrauensenker on 8/21/2024 in #⚡｜serverless
When ttl is not specificed in policy, one gets 500 with {"error":"ttl must be \u003e= 10,000 ms"}
Since ~40 min all my requests with 'executionTimeout': 120000 get this error with HTTP status 500.
here is my repro
curl -v -X POST "https://api.runpod.ai/v1/XXX/run" -H "Authorization: Bearer XXX" -H "Content-Type: application/json" -d '{"input": {"XXX": "XXX"}, "policy": {"executionTimeout": 120000}}'
this used to work previously
also disagrees with https://docs.runpod.io/serverless/endpoints/send-requests#execution-policies ""ttl": int // Time in milliseconds. Must be greater than or equal to 10 seconds. Default is 24 hours. Maximum is one week."
7 replies
RRunPod
•Created by Augenbrauensenker on 3/24/2024 in #⚡｜serverless
Is execution timeout per request or per worker execution?
https://docs.runpod.io/serverless/endpoints/send-requests#--execution-policy
"Execution Timeout: Specifies the maximum duration that a job can run before it's automatically terminated."
The endpoint edit UI says - "Maximum amount of time in seconds a request can run for."
I read the first one as "max lifetime of a worker" - i.e. if it takes 5s to process a request and execution timeout is 60s, the worker will process 12 requests and die.
I read the first one as "if a request takes 60s, the worker will die, but as long as requests take <60s, the worker will run forever"
which one is it?
6 replies
RRunPod
•Created by Augenbrauensenker on 3/24/2024 in #⚡｜serverless
GPU type prioritization seems to have stopped working on 13th of March
I have an endpoint with 3 cheapest GPU types selected in the order of their price (i.e. 4090 is my 3rd option). I noticed that my expenses almost doubled after 13th of March, but the billed GPU time didn't change much. It turned out that before 13th of March the usage of 4090 was close to 0 (which is what I expect - it is my 3rd option). On 13th of March 4090 usage jumped to 50-70% skyrocketing my prices. This is unexpected and unfortunately leads to additional costs for me. For now I removed 4090 as my 3rd option, but this behavior seems abnormal, thus, reaching out to you here.
7 replies