Configure different timeouts in gunicorn for different endpoints?

Question

Gunicorn allows configuring a timeout for requests, as demonstrated in their documentation below. This seems to be a global configuration for the entire application.

Is it possible to configure different timeouts for different endpoints? Perhaps overriding the default timeout on url endpoints that are known to take a long time?

http://docs.gunicorn.org/en/stable/settings.html#timeout

timeout

-t INT, --timeout INT

30

Workers silent for more than this many seconds are killed and restarted.

Generally set to thirty seconds. Only set this noticeably higher if you’re sure of the repercussions for sync workers. For the non sync workers it just means that the worker process is still communicating and is not tied to the length of time required to handle a single request.

Answer 1

There is no easy way to do what you want to do. Probably the best option is to package each endpoint into a separate application, and then launch them with their own separate gunicorn processes / workers with the appropriate timeouts. Then put something like nginx to proxy the endpoints to different gunicorn processes.