explore_json return error that 'an error occured'
See original GitHub issueexplore_json
return error with this content an error occurred
for queries that approximately takes time more than ‘00:01:57’ while the query returns in the sql_lab
.
This issue happens while I increased the webserver timeout
and it’s big enough for that!
Expected results
Show table in explore_json
Actual results
Superset just returns error with this content: an error occured
Screenshots
How to reproduce the bug
- Go to
- Click on ‘…’
- Scroll down to ‘…’
- See error
Environment
(please complete the following information):
- superset version:
master branch from 3 weeks ago
- python version:
3.6
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
- I have checked the superset logs for python stacktraces and included it here as text if there are any.
- I have reproduced the issue with at least the latest released version of superset.
- I have checked the issue tracker for the same issue and I haven’t found one similar.
Additional context
Add any other context about the problem here.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
JSON error handling
In cases where a JavaScript Object Notation (JSON) transaction fails, the API Gateway can use a JSON error to convey error information to...
Read more >What should a JSON service return on failure / error
If the request fails, either because an exception was thrown (e.g. database timeout) or because the request was wrong in some way (e.g....
Read more >How to Fix the Invalid JSON Response Error in WordPress
The WordPress invalid JSON response error happens in the new Block Editor (AKA Gutenberg) when something goes wrong on your site.
Read more >How to Fix SyntaxError: Unexpected token < in JSON at ...
Usually this error is caused when your server returns HTML (which typically begins with <DOCTYPE html> or <html> ) instead of JSON. Valid...
Read more >HTTP status and error codes for JSON | Cloud Storage
Cloud Storage uses the standard HTTP error reporting format for the JSON API. Successful requests return HTTP status codes in the 2xx range....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Issue-Label Bot is automatically applying the label
#bug
to this issue, with a confidence of 0.91. Please mark this comment with 👍 or 👎 to give our bot feedback!Links: app homepage, dashboard and code for this bot.
SUPERSET_WEBSERVER_TIMEOUT
is set to 120 seconds.gunicorn
timeout is set to 150 seconds.gunicorn
–bind “0.0.0.0:8088”
–workers $((2 * $(getconf _NPROCESSORS_ONLN) + 1))
-k gevent
–timeout 150
–limit-request-line 0
–limit-request-field_size 0
–access-logfile ‘-’
–error-logfile ‘-’
superset:app
I’m still getting random timeouts (15 secs, 22 secs,.). Here’s the error we get in the browser as the connection gets dropped by the webserver.
POST superset/explore_json/?form_data=%7B%22slice_id%22%3A62%7D&force=true net::ERR_EMPTY_RESPONSE TypeError: Failed to fetch
Do we need any specific timeout setting in ngnix for the above
SUPERSET_WEBSERVER_TIMEOUT
andgunicorn
timeout settings to work ?