aavanzyl opened a new issue, #27850:
URL: https://github.com/apache/superset/issues/27850
### Bug description
When using SQL Lab to execute a query such as `SELECT * from claims.claim
limit 1`, the UI shows `Pending` and never starts increasing the execution
time.
The following is logged in the browser:
Execute:
`
{
"query": {
"changed_on": "2024-04-02T07:16:18.493787",
"dbId": 1,
"db": "Amazon Redshift (Prod)",
"endDttm": null,
"errorMessage": null,
"executedSql": null,
"id": "9E6eWGcfB",
"queryId": 26748,
"limit": 1,
"limitingFactor": "QUERY",
"progress": 0,
"rows": null,
"schema": null,
"ctas": false,
"serverId": 26748,
"sql": "SELECT * from claims.claim limit 1\n",
"sqlEditorId": "1773",
"startDttm": 1712042178240.671000,
"state": "pending",
"tab": "Untitled Query 1",
"tempSchema": null,
"tempTable": null,
"userId": 1,
"user": "Anton van Zyl",
"resultsKey": null,
"trackingUrl": null,
"extra": {}
}
}
`
We get multiple updated since messages back such as:
`{
"result": [
{
"changed_on": "2024-04-02T07:16:18.242144",
"ctas": false,
"db": "Amazon Redshift (Prod)",
"dbId": 1,
"endDttm": null,
"errorMessage": null,
"executedSql": null,
"extra": {},
"id": "9E6eWGcfB",
"limit": 1000,
"limitingFactor": "UNKNOWN",
"progress": 0,
"queryId": 26748,
"resultsKey": null,
"rows": null,
"schema": null,
"serverId": 26748,
"sql": "SELECT * from claims.claim limit 1\n",
"sqlEditorId": "1773",
"startDttm": "1712042178240.671000",
"state": "pending",
"tab": "Untitled Query 1",
"tempSchema": null,
"tempTable": null,
"trackingUrl": null,
"user": "Anton van Zyl",
"userId": 1
}
]
}
`
But never receive and `/results` call back.
My current remedy is to restart the instance and cache, which seems to
intermittently solve the issue.
This issue only started recently, with us updating to 3.1.0 and then 3.1.1.
I have checked the logs, nothing pops up as out of the ordinary.
### How to reproduce the bug
Go to SQL Lab and run any query will result in the query being stuck in
`Pending`
### Screenshots/recordings
The current UI state being shown to the end user:
### Superset version
3.1.1
### Python version
I don't know
### Node version
I don't know
### Browser
Chrome
### Additional context
We are running the latest 3.1.1 superset from a docker container hosted on
ECS in AWS. The instance size has 12gigs of memory and connects to a Redshift
database.
Superset Caching is set up with Redis 7.1.0 running on elasticache in AWS.
### 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: notifications-unsubscr...@superset.apache.org.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
