saLeox opened a new issue, #19816: URL: https://github.com/apache/superset/issues/19816
It's known that the Redis cache is already applied in query for query_context and viz, but there is a situation that makes it doesn’t work well, that’s when multi concurrent query requests to one dashboard or chart, come in at the same time, from different users. It will cause duplicated query request to our query engine, because the cache is not ready yet. As a result, it brings burden to cluster and waste resources. Since the superset is natively distributed, and the async task is supposed to run in multiple celery works, we come up with an assumption that, maybe the distributed lock can help, which should be acquired before cache retrieve and released after query complete, to make the queries with the same cache key execute in a serial way, instead of a concurrent way. ### 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. -- 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]
