bossman
RRunPod
•Created by bossman on 11/18/2024 in #⚡｜serverless
job timed out after 1 retries
Been seeing this a ton on my endpoint today resulting in being unable to return images.
response_text: "{"delayTime":33917,"error":"job timed out after 1 retries","executionTime":31381,"id":"sync-80dbbd6d-309c-491f-a5d0-2bd79df9c386-e1","retries":1,"status":"FAILED","workerId":"a42ftdfxrn1zhx"}
26 replies
RRunPod
•Created by bossman on 11/13/2024 in #⚡｜serverless
Why is Runsync returning status response instead of just waiting for image response?
My runsync requests are getting messed up by runpod returning a sync equivalent response (with 'IN_PROGRESS' status and id showing). I need to just return the image, or a failure, not the status using runsync. If I want the status I would just use 'run'. Any idea why this is happening and how to prevent it?
For reference, this is for request that generally run for 5-18 seconds to completion.
delayTime: 196
id: "sync-dad6d689-1106-4f29-9aea-a843c6741687-u1"
status: "IN_PROGRESS"
workerId: "0q4lddfhys3oxk"
9 replies
RRunPod
•Created by bossman on 11/12/2024 in #⚡｜serverless
comfy
getting message 'throttled waiting for GPU to become available' even though I have 4 endpoints selected with high and medium availability.
2 replies