Augenbrauensenker
RRunPod
•Created by Augenbrauensenker on 11/20/2024 in #⚡｜serverless
Runpod requests fail with 500
thank you for the fix! Really curious what was the cause 🙂
6 replies
RRunPod
•Created by Augenbrauensenker on 11/20/2024 in #⚡｜serverless
Runpod requests fail with 500
seems fixed, i can also open my endpoint in UI again.
6 replies
RRunPod
•Created by Augenbrauensenker on 11/20/2024 in #⚡｜serverless
Runpod requests fail with 500
looks like all requests to my prod endpoint fail with 500
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"}
They told me that fix has been deployed.
7 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"}
someone contacted me privately and said they are fixing the issue
7 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"}
setting ttl in policy explicitly fixed the issue for me
7 replies
RRunPod
•Created by Augenbrauensenker on 3/24/2024 in #⚡｜serverless
Is execution timeout per request or per worker execution?
I would appreciate the answer. Thank you!
6 replies
RRunPod
•Created by Augenbrauensenker on 3/24/2024 in #⚡｜serverless
GPU type prioritization seems to have stopped working on 13th of March
thank you, that explains it, unfortunately, i haven't seen this requirement anywhere
i think proper UI would be to disable gpu selection if there are > 0 workers and unlock it only when there is 0 workers
7 replies
RRunPod
•Created by Augenbrauensenker on 3/24/2024 in #⚡｜serverless
GPU type prioritization seems to have stopped working on 13th of March
4090 still gets 25% of billing time
7 replies
RRunPod
•Created by Augenbrauensenker on 3/24/2024 in #⚡｜serverless
GPU type prioritization seems to have stopped working on 13th of March
Now I think that GPU selection is just broken - I've removed my 3rd option (4090) completely hours ago and I still get jobs ran on 4090 as of right now and pay price of 4090. I suspect these might be old workers still cached on 4090, but it has been ~7h since I change the selection, so I expect these workers to be rescheduled or not used at all.
7 replies