dosubot[bot] commented on issue #31615: URL: https://github.com/apache/superset/issues/31615#issuecomment-2561632003
<!-- Answer --> I found a couple of similar discussions that might be relevant to your issue: 1. [Redis CROSSSLOT keys request don't hash to the same slot](https://github.com/apache/superset/discussions/28606) - This discussion is still open and might provide insights into Redis configuration issues <sup>[[1]](https://github.com/apache/superset/discussions/28606)</sup>. 2. [Understanding how caching helps in auto-refreshing dashboards](https://github.com/apache/superset/discussions/20803) - This is another open discussion that could offer some understanding of caching mechanisms in Superset <sup>[[2]](https://github.com/apache/superset/discussions/20803)</sup>. Regarding your configuration, here are a few things to consider: 1. **Redis Configuration**: Ensure that your Redis server is running and accessible at the specified host and port. You can test connectivity using a Redis client. 2. **Cache Configuration**: Your `DATA_CACHE_CONFIG` is set to use `SupersetMetastoreCache`, which is different from Redis. If you intend to use Redis for all caching, you might want to align this configuration with your `FILTER_STATE_CACHE_CONFIG` by using `RedisCache` instead. 3. **Celery and Redis**: Ensure that both Celery and Redis are properly configured and running. Check the logs for any errors related to task execution or result storage. 4. **Cache Key Prefixes**: Make sure that the `CACHE_KEY_PREFIX` values are unique and correctly set to avoid any key collisions. 5. **Superset Logs**: Review the Superset logs for any error messages or warnings that might indicate what is going wrong with the caching mechanism. If these steps do not resolve the issue, you might want to explore the discussions mentioned above for additional insights or consider testing with a simplified configuration to isolate the problem. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/d6827a25-0170-40ef-80ad-6e4a3cb86332?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/d6827a25-0170-40ef-80ad-6e4a3cb86332?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/d6827a25-0170-40ef-80ad-6e4a3cb86332?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/d6827a25-0170-40ef-80ad-6e4a3cb86332?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d6827a25-0170-40ef-80ad-6e4a3cb86332?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/d6827a25-0170-40ef-80ad-6e4a3cb86332?feedback_type=other)</sup> -- 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]
