Runpod•2y ago•

20 replies

Request stuck in "IN_QUEUE" status

Hi,
I tried to setup a endpoint for "rembg" package using cog. It seems to run fine locally, but when I hit the serverless endpoint the request is always "IN_QUEUE" even though the logs shows that the server is up and running. Do you know what could be the issue?

ashley•1/15/24, 8:54 PM

Are all your workers throttled?

mrmvpOP•1/15/24, 8:58 PM

Ah you mean throttled by cpu utilization?

mrmvpOP•1/15/24, 9:00 PM

ashley•1/15/24, 9:02 PM

Why did you set max workers to 1? That is a bad idea, leave it at defaulrt of 3.

ashley•1/15/24, 9:03 PM

The default of 3 is the sane default, setting it to 1 will cause you endless issues, nightmares and a world of pain.

mrmvpOP•1/15/24, 9:09 PM

Ah I see, it was initially 3 but I was still facing the same issue and it was costing quite a bit so I switched it to 1

Mmrmvp Ah I see, it was initially 3 but I was still facing the same issue and it was co...

ashley•1/15/24, 9:13 PM

You don't pay for max workers, only for active workers. With max workers you only pay for the requests.

mrmvpOP•1/15/24, 9:20 PM

Okay set it back to 3. But how do i resolve the issue of the request being stuck in "IN_QUEUE"?

Mmrmvp Okay set it back to 3. But how do i resolve the issue of the request being stuck...

ashley•1/15/24, 9:22 PM

Are all 5 workers throttled?

mrmvpOP•1/15/24, 9:30 PM

Nope

mrmvpOP•1/15/24, 9:30 PM

ashley•1/15/24, 9:32 PM

Are any of your requests actually processing successfully?

mrmvpOP•1/15/24, 9:32 PM

Nope

ashley•1/15/24, 9:33 PM

Then there is something wrong with your handler, click on one of the workers and check the logs.

mrmvpOP•1/15/24, 9:34 PM

hmm I see this. When I run the docker container locally, it processes the request successfully. Not unable to get it work on serverless

navin_hariharan•1/16/24, 3:10 AM

@mrmvp Mind sending your rp hander?

navin_hariharan•1/16/24, 3:10 AM

There is something erong with it!

Mmrmvp hmm I see this. When I run the docker container locally, it processes the reques...

ashley•1/16/24, 5:44 AM

Looks like the /health-check/health-check API is not working and resulting in an HTTP 404 not found, and then looks like you are wrapping the health check API call in a

try

try

, exceptexcept block and which tries to access the

status

status

field of the JSON response from /health-check/health-check but its failing because

status

status

does not exist within the HTTP 404 response and throws a KeyErrorKeyError exception as a result.

mrmvpOP•1/16/24, 8:15 AM

I have been following this tutorial https://blog.runpod.io/replicate-cog-migration/
I have not changed anything in the handler code inside the cog-workercog-worker

RunPod Blog

Serverless | Migrating and Deploying Cog Images on RunPod Serverles...

Switching cloud platforms or migrating existing models can often feel like a Herculean task, especially when it necessitates additional developmental efforts. This guide aims to simplify this process for individuals who have deployed models via replicate.com or utilized the Cog framework. Through a few straightforward steps, you'll learn how

Request stuck in "IN_QUEUE" status

Similar Threads

Similar Threads

Similar Threads