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

Cache not invalidated after new submissions are processed #2

Open
jvendetti opened this issue Jan 18, 2018 · 0 comments
Open

Cache not invalidated after new submissions are processed #2

jvendetti opened this issue Jan 18, 2018 · 0 comments
Labels

Comments

@jvendetti
Copy link
Member

We've had several reports from the developers of the EDAM ontology where they upload a new ontology submission and the user interface only shows the submission status as uploaded. After waiting (sometimes as long as 24 hours), they're never able to see the status as anything other than uploaded, i.e., the data for the new submission never becomes visible.

I've reproduced this behavior in our production environment on two separate occasions, and observed the following:

  • It doesn't matter if you are logged in our out. The new submission shows as "uploaded" for both cases.
  • Clearing the browser cache has no effect.
  • Manually clearing BioPortal's goo and HTTP caches from the administrative page has no effect.

The only way I was able to get the new data to become visible in the UI was to click the "Flush UI Cache" button on the administrative page, which clears the front end in-memory cache (memcached).

I've also verified (by looking at the production parsing logs), that the EDAM ontology is relatively small and the system has no difficulty during the parsing process. From start to finish, we process the ontology in roughly 12 minutes.

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

No branches or pull requests

1 participant