ExposuresProvider / icees-api

MIT License
2 stars 8 forks source link

ICEES redis database cache could get out of sync with database #230

Closed hyi closed 1 month ago

hyi commented 2 years ago

To address issue #228, I found the root cause for this issue was that the redis database cache was out of sync with the database so the cohorts 3 to 7 were not in the cache although they were in the database. I copied the database from Sterling PVC to my local computer, and all cohort functionalities worked as expected. The fix to this issue was to remove the redis database cache PVC from Sterling and redeploy ICEES API in Sterling. We suspect the database cache out of sync issue may have resulted from a network error in Sterling which could be associated with some Sterling maintenance event, and hope this issue will not crop up again. This issue serves as a reminder in case the issue do crop up again in the future so that we have the context for fixing it and also look into the problem deeply to prevent it from happening again.

hyi commented 1 month ago

This issue has never reoccurred for over 2 years, so closing this issue for now.