ivanonair opened a new issue, #31978: URL: https://github.com/apache/superset/issues/31978
### Bug description When I use DuckDB to connect to MINIO to read data, I often encounter (not always) the following error: > "DB engine Error > This may be triggered by: Issue 1011 - Superset encountered an unexpected error." or sometime error msg are > "upstream connect error or disconnect/reset before headers. reset reason: connection termination" This seems to be related to having multiple filters on a dashboard. I observed that to generate the dropdown menu for each filter, a distinct SQL query is executed on the dataset for each filter. I suspect that this is causing many concurrent queries to be executed simultaneously when the dashboard is opened. And there is also an error msg on superset server: > duckdb.duckdb.InvalidInputException: Invalid Input Error: No open result set. The current probability of error occurrence is about fifty-fifty without changing any settings, not occur every time. This leads to suspicions that it might be an issue with the rate limit or the number of threads. In the article below, I saw that when using duckdb.connect(:default:), it might induce error since running queries concurrently on the same connection is not supported. > duckdb.duckdb.InvalidInputException: Invalid Input Error: Attempting to execute an unsuccessful or closed pending query result [](https://github.com/duckdb/duckdb/issues/13498) However, this is different from the error message I received, and I'm not sure if it's related. Has anyone else using Superset + DuckDB encountered a similar issue? Thanks." ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.10 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [x] I have searched Superset docs and Slack and didn't find a solution to my problem. - [x] I have searched the GitHub issue tracker and didn't find a similar bug report. - [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
