Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Charts data does not update based on cache timeout, refreshing the charts doesn't work #17240

Closed
3 tasks done
spouria opened this issue Oct 27, 2021 · 5 comments
Closed
3 tasks done
Labels
#bug Bug report

Comments

@spouria
Copy link

spouria commented Oct 27, 2021

I have set up superset using mysql and redis on ubuntu server. I have set these config in my config file:

SQLALCHEMY_DATABASE_URI = '[my mysql connection]'
DATA_DIR = os.path.join(os.path.dirname(file), 'data_dir')

CACHE_DEFAULT_TIMEOUT = 600
CACHE_CONFIG = {
'CACHE_TYPE': 'redis',
'CACHE_DEFAULT_TIMEOUT': 600,
'CACHE_KEY_PREFIX': 'superset_',
'CACHE_REDIS_HOST': 'localhost',
'CACHE_REDIS_PORT': 6379,
'CACHE_REDIS_DB': 1,
'CACHE_REDIS_URL': 'redis://localhost:6379/1'
}

I expect the cache to be 10 minutes for my charts, so the dashboard will be updated with new data from my database every 10 minutes. However it updates them every 24 hours and does not use the cache timeout. It neither updates the charts when I use "force refresh' on a chart. However, when I use the 'explore chart' and re-save it, it gets the new data from the database.

How to reproduce the bug

1.set up the superset with these config.
2- create a chart.
3- add some new records to the data source.
4- go to the dashboard after the the time of cache timeout
5- refresh the page

Expected results

The charts are updated with new data added to the datasource

Actual results

The charts are not updated. They will be updated tomorrow.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

(please complete the following information):

  • browser type and version: firefox 93.0
  • superset version: 0.38.1
  • python version: 3.6.7
  • node.js version: 14.16.0
  • redis-server version: 5:4.0.9

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • 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.

@spouria spouria added the #bug Bug report label Oct 27, 2021
@jkleinkauff
Copy link

jkleinkauff commented Nov 7, 2021

Hello! Did you find any solution for this?

@spouria
Copy link
Author

spouria commented Nov 10, 2021

Hello! Did you find any solution for this?

No, unfortunately it still ignores all the cache settings and dashboards get updated every 24 hours.

@stale
Copy link

stale bot commented Apr 17, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@rusackas
Copy link
Member

This issue sounds disconcerting, but is also a bit of an antique. Is anyone still encountering this in current era versions of Superset, or is it safe to close out?

@stale stale bot removed the inactive Inactive for >= 30 days label Jan 13, 2023
@rusackas
Copy link
Member

Closing this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions (currently 3.x) please re-open this issue, open a new Issue with updated context, or raise a PR to address the problem. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

3 participants