Skip to content

Instantly share code, notes, and snippets.

@pcolazurdo

pcolazurdo/readme.md

Created August 6, 2017 09:47
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save pcolazurdo/f02102e54206bf32e7e5ab33db7df51e to your computer and use it in GitHub Desktop.
Save pcolazurdo/f02102e54206bf32e7e5ab33db7df51e to your computer and use it in GitHub Desktop.
Download ZIP
Raw
readme.md

If you have problems when downloading large results sets from reDash it may be you are running against the default 30 seconds timeout in gunicorn. To solve this you can edit your:

/opt/redash/supervisord/supervisord.conf

and change:

[program:redash_server]
command=/opt/redash/current/bin/run gunicorn -b 127.0.0.1:5000 --name redash -w 4 redash.wsgi:app

to

command=/opt/redash/current/bin/run gunicorn -b 127.0.0.1:5000 --name redash -t 300 -w 4 redash.wsgi:app

Hope it helps, Pablo

@hara5
Copy link

hara5 commented May 8, 2019

Hey Pablo,
any idea, how to configure this with redash docker setup?

@acondrat
Copy link

Seems like you can set it with the GUNICORN_CMD_ARGS environment variable.

GUNICORN_CMD_ARGS="--timeout=300"

https://docs.gunicorn.org/en/stable/settings.html

@zachliu
Copy link

zachliu commented Mar 8, 2021

Seems like you can set it with the GUNICORN_CMD_ARGS environment variable.

GUNICORN_CMD_ARGS="--timeout=300"

https://docs.gunicorn.org/en/stable/settings.html

redash is using gunicorn version 19.9.0 which unfortunately doesn't allow us to --print-config to see the resolved settings

does anyone know how to verify if GUNICORN_CMD_ARGS="--timeout=300" actually works?

@isabella0428
Copy link

Currently, here is a environment variable REDASH_GUNICORN_TIMEOUT: 300 in docker-compose.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment