avalanchecrusader opened a new issue, #30250: URL: https://github.com/apache/superset/issues/30250
### Bug description Hi everyone! Perhaps someone has come around such an issue. We are currently migrating our data base from GBQ to Trino, hence nececcity of reconnecting uor Superset instance arises. I have an overview dashboard with quite a bunch of filters and elements (total count on 'home' page comes to 45) and it tends to collapse Superset instance on inititalization. Superset runs in docker/k8s. Together with our DevOps team we tried a couple of things like: - allocating more resourses - increasing timeouts - increasing pool size and max overflow size parameters - initialyzing sentry Nothing has yet hepled though. Log lso shows no errors. Any thoughts on why it can happen and how it can be solved? ### How to reproduce the bug - ### Screenshots/recordings _No response_ ### Superset version 3.1.3 ### 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]
