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

Investigate cache invalidation problems #87

Open
philipn opened this issue Oct 20, 2016 · 0 comments
Open

Investigate cache invalidation problems #87

philipn opened this issue Oct 20, 2016 · 0 comments

Comments

@philipn
Copy link
Member

philipn commented Oct 20, 2016

Notes from before:

This looks like a caching issue, similar (if not identical) to #746, #769. With #769, this was caused (or perhaps simply fixed) by a lack of a restart of the celery service, which does the cache invalidation after page save.

Editing the page in question did not result in a cache refresh, as per report above. Restarting the celery service (service celery restart) followed by editing the page resulted in a cache refresh. My current hypothesis is that a fab deploy was done and the celery service wasn't restarted at some point.

Looking at the celery log at /var/log/celery doesn't show anything illuminating about cache invalidation.


fab deploy is restarting the celery service, so I'm not immediately sure why a manual restart fixes the problem. Perhaps it's the sitemaps code crashing celery, so I'll take a look at that now.

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

No branches or pull requests

1 participant