dervish54 opened a new issue, #30286:
URL: https://github.com/apache/superset/issues/30286

   ### Bug description
   
   I guess the following issues are related to each other:
   
   1. Superset regularly crashes with the `error: sqlalchemy.exc.TimeoutError: 
QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 
30.00`. 
   
   2. Database Locks are accumulating in the Superset database. Here is an 
example:
   ```
   Current locks: 124
   waitstart, locktype, relation::regclass, mode, objsubid, granted
   (None, 'relation', 'pg_stat_activity', 'AccessShareLock', None, True)
   (None, 'relation', 'pg_locks', 'AccessShareLock', None, True)
   (None, 'virtualxid', None, 'ExclusiveLock', None, True)
   (None, 'relation', 'ab_user', 'AccessShareLock', None, True)
   (None, 'relation', 'ab_view_menu_name_key', 'AccessShareLock', None, True)
   (None, 'relation', 'ab_view_menu_pkey', 'AccessShareLock', None, True)
   <...>
   ```
   
   3. Importing charts and dashboards does not work When trying to import 
charts and dashboards to a new Superset server with the same configuration 
(except for the password and secret key), I get an error.
   
   4. The version in the Settings dropdown is shown as "Version: 0.0.0-dev". I 
am sure this should not be the case.
   
   
   
   ### How to reproduce the bug
   
   
   1. `git clone --depth=1 https://github.com/apache/superset.git`
   2. `cd superset`
   3.  make changes to docker/.env: `POSTGRES_PASSWORD`, `DATABASE_PASSWORD`, 
`SUPERSET_LOAD_EXAMPLES=no` and `SUPERSET_SECRET_KEY`
   4. docker compose -f docker-compose-non-dev.yml up -d
   5. Login and face problems from the list above.
   
   
   ### Screenshots/recordings
   
   
   
![image](https://github.com/user-attachments/assets/67cc1788-b882-491e-8b23-5ee615d7f237)
   
   
![image](https://github.com/user-attachments/assets/650a7edd-2457-46ec-a012-7d55f69ca2ac)
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   ```
   superset_app          |   File 
"/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 894, in 
_checkout
   superset_app          |     fairy = _ConnectionRecord.checkout(pool)
   superset_app          |   File 
"/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 493, in 
checkout
   superset_app          |     rec = pool._do_get()
   superset_app          |   File 
"/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/impl.py", line 134, in 
_do_get
   superset_app          |     raise exc.TimeoutError(
   superset_app          | sqlalchemy.exc.TimeoutError: QueuePool limit of size 
5 overflow 10 reached, connection timed out, timeout 30.00 (Background on this 
error at: https://sqlalche.me/e/14/3o7r)
   superset_app          | 2024-09-10 
13:04:48,939:ERROR:superset.views.error_handling:QueuePool limit of size 5 
overflow 10 reached, connection timed out, timeout 30.00 (Background on this 
error at: https://sqlalche.me/e/14/3o7r)
   superset_app          | Traceback (most recent call last):
   superset_app          |   File 
"/usr/local/lib/python3.10/site-packages/flask/app.py", line 1484, in 
full_dispatch_request
   ```
   
   ### 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]

Reply via email to