praveenhalian commented on issue #5993:
URL: https://github.com/apache/superset/issues/5993#issuecomment-2652881409

   I hope this email finds you well.
   I am reaching out for assistance with an ongoing issue we are facing with 
our Superset deployment. We have configured various timeout settings for SQL 
Lab, Gunicorn, and other related parameters, but we continue to encounter a 504 
Gateway Timeout (60000ms) error when performing queries through the Superset 
portal.
   Issue Details:
   Error: 504 Gateway Timeout (60000ms)
   Superset Version: [insert version here]
   Timeout Configuration: We have updated the following timeout values in the 
superset_config.py:
   SQLLAB_TIMEOUT = 1800
   SQLLAB_ASYNC_TIME_LIMIT_SEC = 1800
   SUPERSET_WEBSERVER_TIMEOUT = 1800
   SUPERSET_SQLALCHEMY_TIMEOUT = 1800
   GUNICORN_TIMEOUT = 1800
   Despite setting these values, the portal is still enforcing a 60-second 
timeout limit.
   Troubleshooting Steps Taken:
   Cleared Superset cache using superset init.
   Restarted the Superset deployment after changes.
   Ensured the environment variable FRONTEND_TIMEOUT was set correctly.
   Cleared browser cache and tested in incognito mode.
   Verified Nginx and Ingress timeout settings.
   Checked logs for any errors related to timeouts.
   Despite these steps, the timeout issue persists, and SQL queries are still 
getting cut off after 60 seconds.
   Request:
   I would appreciate your assistance in:
   Confirming whether there are any additional configuration settings or steps 
needed to apply a 30-minute timeout effectively.
   Identifying if there are any issues with how the timeout settings are being 
processed within the Superset environment.
   Please let me know if you require any additional information or logs from my 
side to help diagnose and resolve this issue.
   Thank you for your assistance.
   @Kolliderrr 
   
   
   
   
   
   
   
   
   
   
   
   
   
   Message Ghazi Triki


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to