Open dervish54 opened 5 days ago
I found a similar unsolved discussion and some related closed issues that might help you:
Similar Unsolved Discussion:
Related Closed Issues:
sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 10 reached
:
superset_config.py
:
SQLALCHEMY_ENGINE_OPTIONS = {
"pool_size": 20,
"max_overflow": 30,
"pool_timeout": 60,
}
This should help mitigate the connection pool limit issue [4].
Database Locks Accumulating:
class CreateDistributedLock(BaseDistributedLockCommand):
lock_expiration = timedelta(seconds=30)
...
Regularly monitor and clean up expired locks to prevent accumulation [5].
Importing Charts and Dashboards:
# Import databases
# Import datasets
# Import charts
# Import dashboards
Refer to the detailed import steps provided in the Superset documentation [6][7][8][9].
Version Displayed as "0.0.0-dev":
docker-compose-non-dev.yml
configuration. Verify the build context, environment files, and volumes:
build:
context: .
target: non-dev
env_file:
- path: docker/.env
- path: docker/.env-local
volumes:
- ./docker:/app/docker
- superset_home:/app/superset_home
These configurations can affect the version display [10].
By addressing these configurations and settings, you should be able to resolve the issues you're facing with Superset.
To continue talking to Dosu, mention @dosu.
Can't say I've run into this one. Assigning to @betodealmeida, but curious if @villebro or @mistercrunch have any advice here.
Which version is this on? latest master?
@mistercrunch
Which version is this on? latest master?
Yes:
~/superset# git branch
* master
The repository was cloned on September 11. I followed this instruction https://superset.apache.org/docs/installation/docker-compose/#installing-superset-locally-using-docker-compose
Did you git pull since then, master mais not be fully stable at all time and I think there may be a recent fix.
@mistercrunch When testing the export-import of dashboards between different instances of Superset, I raised another one in a similar way, it was 4-5 days ago. The same problem was observed in that new instance. Now I'm thinking about using earlier versions. Is there any advice on which version to prefer according to the stability criterion?
Here's the PR you want to make sure is in your branch, landed last week and should fix a regression around transaction isolation / lock. You can check with git log
whether it was in there or not.
https://github.com/apache/superset/pull/30174
Latest official stable release is 4.0.2, so you can git checkout 4.0.2
if you prefer, and there's 4.1.0rc3
too if you want to make sure the issues you are reporting are going to be fixed in 4.1.0
Beyond the fix above, and as pointed out by the bot, It's a good idea to make sure your SQLALCHEMY_ENGINE_OPTIONS
has a necessarily big pool_size
+ max_overflow
to facilitate for all gunicorn threads. Say you have 20 gunicorn threads, your combined pool_size
and max_overflow
should not be less than 20 to ensure there's sufficient connections in the pool during high load.
Bug description
I guess the following issues are related to each other:
Superset regularly crashes with the
error: sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30.00
.Database Locks are accumulating in the Superset database. Here is an example:
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.
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
git clone --depth=1 https://github.com/apache/superset.git
cd superset
POSTGRES_PASSWORD
,DATABASE_PASSWORD
,SUPERSET_LOAD_EXAMPLES=no
andSUPERSET_SECRET_KEY
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
Checklist