dharmic6 opened a new issue #16002:
URL: https://github.com/apache/superset/issues/16002
While DB async query execution is enabled and running SQL statements
parallelly, the celery worker responds with a timeout after the
SQLLAB_ASYNC_TIME_LIMIT_SEC is reached, however, Superset still keeps the
process in a pending state and doesnt move into next task that is in waiting
state(ready to execute)
Celery worker: celery worker --app=superset.tasks.celery_app:app
--pool=prefork -O fair --loglevel=DEBUG --autoscale=50,1
SQLLAB_ASYNC_TIME_LIMIT_SEC = 300
RESULTS_BACKEND = RedisCache(host=CELERY_REDIS_HOST,
port=REDIS_PORT, key_prefix=CACHE_PREFIX)
### Expected results
Once celery worker timeout, superset should exit the process and move to the
next ready task
### Actual results
superset waits for at pending state even though celery worker times out.
#### Screenshots
#### How to reproduce the bug
1. Enable Async query execution for a database, with celery workers.
2. Go to SQL lab and run a query that returns a result in say 3 minutes, run
at least 5 tasks like this.
3. After timeout is reached, the Celery worker responds with a hard time out
reached, exiting the process.
3. Superset UI still shows the process as in pending state.
4. Stop a running query on Sql lab UI and run a small SQL( which returns the
result immediately), Superset still shows the process in pending state and
never gets the result back.
### Environment
(please complete the following information):
- superset version: `1.2`
- python version: `3.7`
- node.js version: `v16.5.0`
- any feature flags active:
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [x ] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [ x] I have reproduced the issue with at least the latest released version
of superset.
- [ x] I have checked the issue tracker for the same issue and I haven't
found one similar.
### Additional context
Add any other context about the problem here.
--
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]
