From eeca2d034f9597f4d7f92b83682f3fec2c349797 Mon Sep 17 00:00:00 2001 From: Riccardo Magliocchetti Date: Wed, 27 Sep 2017 17:20:59 +0200 Subject: [PATCH] docs: QUERY_TIMEOUT_THRESHOLD is gone (#3537) --- docs/faq.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq.rst b/docs/faq.rst index 2a0d03d47d2d4..e5d2bb3c17079 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -67,9 +67,9 @@ There are many reasons may cause long query timing out. ``superset runserver -t 300`` -- If you are seeing timeouts (504 Gateway Time-out) when loading dashboard or explore slice, you are probably behind gateway or proxy server (such as Nginx). If it did not receive a timely response from Superset server (which is processing long queries), these web servers will send 504 status code to clients directly. Superset has a client-side timeout limit to address this issue. If query didn't come back within clint-side timeout (45 seconds by default), Superset will display warning message to avoid gateway timeout message. If you have a longer gateway timeout limit, you can change client-side timeout limit settings from ``/superset/superset/assets/javascripts/constants.js`` file and rebuild js package: +- If you are seeing timeouts (504 Gateway Time-out) when loading dashboard or explore slice, you are probably behind gateway or proxy server (such as Nginx). If it did not receive a timely response from Superset server (which is processing long queries), these web servers will send 504 status code to clients directly. Superset has a client-side timeout limit to address this issue. If query didn't come back within clint-side timeout (60 seconds by default), Superset will display warning message to avoid gateway timeout message. If you have a longer gateway timeout limit, you can change the timeout settings in ``superset_config.py``: - ``export const QUERY_TIMEOUT_THRESHOLD = 45000;`` + ``SUPERSET_WEBSERVER_TIMEOUT = 60`` Why is the map not visible in the mapbox visualization?