Anton-Kartashev opened a new issue, #32588:
URL: https://github.com/apache/superset/issues/32588
### Bug description
Hello
I'm setup Redis for caching
CACHE_CONFIG = {
"CACHE_TYPE": "RedisCache",
"CACHE_DEFAULT_TIMEOUT": 3600,
"CACHE_KEY_PREFIX": "superset_",
"CACHE_REDIS_URL": CACHE_REDIS_URL,
}
DATA_CACHE_CONFIG = CACHE_CONFIG
When I'm accessing from UI I got redis key:
superset_e23a1c62312312a397c45c3d33e528a2
but when I'm running celery task I have:
superset_b0785f6387364685c0fc67b2c738a54e
and warmup task not updated dashboard. I have version 4.1.1 with patched
cache.py for working CSRF tokens.
Celery config:
```
class CeleryConfig(object):
imports = (
"superset.sql_lab",
"superset.tasks.scheduler",
"superset.tasks.cache",
)
broker_url = CACHE_REDIS_URL
result_backend = CACHE_REDIS_URL
worker_concurrency = 10
broker_connection_retry_on_startup = True
task_acks_late = True
beat_schedule = {
'cache-warmup-1h': {
'task': 'cache-warmup',
'schedule': crontab(minute=0, hour='*'),
'kwargs': {
'strategy_name': 'dashboard_tags',
'tags': ['warmup_1h'],
},
},
'cache-warmup-3h': {
'task': 'cache-warmup',
'schedule': crontab(minute=0, hour='*/3'),
'kwargs': {
'strategy_name': 'dashboard_tags',
'tags': ['warmup_3h'],
},
},
'cache-warmup-5m': {
'task': 'cache-warmup',
'schedule': crontab(minute='*/5', hour='*'),
'kwargs': {
'strategy_name': 'dashboard_tags',
'tags': ['warmup_5m'],
},
},
'cache-warmup-15m': {
'task': 'cache-warmup',
'schedule': crontab(minute='*/15', hour='*'),
'kwargs': {
'strategy_name': 'dashboard_tags',
'tags': ['warmup_15m'],
},
},
}
CELERY_CONFIG = CeleryConfig
```
Is anyone faced this some issues? And hot to solve this.
### Screenshots/recordings
_No response_
### Superset version
4.1.1
### Python version
3.11
### Node version
Not applicable
### Browser
Not applicable
### Additional context
_No response_
### 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: [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]
