dosubot[bot] commented on issue #30286:
URL: https://github.com/apache/superset/issues/30286#issuecomment-2352608386
<!-- Answer -->
I found a similar unsolved discussion and some related closed issues that
might help you:
1. **Similar Unsolved Discussion**:
- ['Version: 0.0.0-dev' even though I'm using non-dev yml — what went
wrong?](https://github.com/apache/superset/discussions/30267)
<sup>[[1]](https://github.com/apache/superset/discussions/30267)</sup>.
2. **Related Closed Issues**:
- [Superset_init crashes due to failures in migration
scripts](https://github.com/apache/superset/issues/25699)
<sup>[[2]](https://github.com/apache/superset/issues/25699)</sup>.
- [[Import] Unable to import Dashboard using Rest
API](https://github.com/apache/superset/issues/20655)
<sup>[[3]](https://github.com/apache/superset/issues/20655)</sup>.
### Addressing Your Issues:
1. **`sqlalchemy.exc.TimeoutError: QueuePool limit of size 5 overflow 10
reached`**:
- This error indicates that the connection pool limit is being reached.
You can increase the pool size and timeout settings in your
`superset_config.py`:
```python
SQLALCHEMY_ENGINE_OPTIONS = {
"pool_size": 20,
"max_overflow": 30,
"pool_timeout": 60,
}
```
This should help mitigate the connection pool limit issue
<sup>[[4]](https://github.com/apache/superset/blob/master/superset/config.py)</sup>.
2. **Database Locks Accumulating**:
- Superset handles database locks using a distributed lock mechanism.
Ensure that the lock expiration is set appropriately and that expired locks are
being cleaned up:
```python
class CreateDistributedLock(BaseDistributedLockCommand):
lock_expiration = timedelta(seconds=30)
...
```
Regularly monitor and clean up expired locks to prevent accumulation
<sup>[[5]](https://github.com/apache/superset/blob/master/superset/commands/distributed_lock/create.py)</sup>.
3. **Importing Charts and Dashboards**:
- Ensure that you are importing databases, datasets, and charts in the
correct order before importing dashboards. Follow the detailed steps for
importing:
```python
# Import databases
# Import datasets
# Import charts
# Import dashboards
```
Refer to the detailed import steps provided in the Superset
documentation
<sup>[[6]](https://github.com/apache/superset/blob/master/superset/commands/dashboard/importers/v1/__init__.py)</sup><sup>[[7]](https://github.com/apache/superset/blob/master/superset/commands/dashboard/importers/v0.py)</sup><sup>[[8]](https://github.com/apache/superset/blob/master/superset/commands/importers/v1/assets.py)</sup><sup>[[9]](https://github.com/apache/superset/blob/master/superset/dashboards/api.py)</sup>.
4. **Version Displayed as "0.0.0-dev"**:
- Ensure you are using the correct `docker-compose-non-dev.yml`
configuration. Verify the build context, environment files, and volumes:
```yml
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
<sup>[[10]](https://github.com/apache/superset/blob/master/docker-compose-non-dev.yml)</sup>.
By addressing these configurations and settings, you should be able to
resolve the issues you're facing with Superset.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
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: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
