CODEWITHSUNDEEP
djangogunicorn
Sassan
Sassan

Reputation: 2337

Gunicorn not responding

I'm using Gunicorn to serve a Django application, it was working alright till I changed its timeout from 30s to 900000s, I had to do this because I had a usecase in which a huge file needed to get uploaded and processed (process taking more than 30m in some cases) but after this change Gunicorn goes unresponsive after few hours, I guess the problem is all workers (being 30) will be busy with some requests after this amount of time, the weird thing is it happens even if I don't run that long request at all and it happens with normal exploring in django admin. I wanna know if there's a way to monitor requests on gunicorn and see workers are busy with what requests, I wanna find out the requests that's making them busy. I tried --log-file=- --log-level=debug but it doesn't tell anything about requests, I need more detailed logs.

Upvotes: 12

Views: 5884

Answers (2)

user3681414
user3681414

Reputation: 109

While I am also looking for a good answer for how to see how many workers are busy, you are solving this problem the wrong way. For a task that takes that long you need a worker, like Celery/RabbitMQ, to do the heavy lifting asynchronously, while your request/response cycle remains fast.

I have a script on my site that can take 5+ minutes to complete, and here's a good pattern I'm using:

  1. When the request first comes in, spawn the task and simply return a HTTP 202 Accepted. Its purpose is "The request has been accepted for processing, but the processing has not been completed."
  2. Have your front-end poll the same endpoint (every 30 seconds should suffice). As long as the task is not complete, return a 202
  3. Eventually when it finishes return a 200, along with any data the front-end might need.

For my site, we want to update data that is more than 10 minutes old. I pass the Accept-Datetime header to indicate how old of data is acceptable. If our local cached copy is older than that, we spawn the task cycle.

Upvotes: -1

Drakes
Drakes

Reputation: 23670

From the latest Gunicorn docs, on the cmd line/script you can use:

--log-file - ("-" means log to stderr)
--log-level debug

or in the config file you can use:

errorlog = '-'
accesslog = '-'
loglevel = 'debug'

but there is no mention of the parameter format you specified in your question:

--log-file=- 
--log-level=debug

The default logging for access is 'None' (ref), so shot in the dark, but this may explain why are not receiving detailed log information. Here is a sample config file from the Gunicorn source, and the latest Gunicorn config docs.

Also, you may want to look into changing your logging configuration in Django.

Upvotes: 5

Related Questions