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

Characterize and capture as an issue the persistence cache out-of-service problem #1453

Open
sheridancbio opened this issue Jan 21, 2025 · 0 comments
Labels
backend-scrum items centered around engineering activities bug Something isn't working Pipeline Maintenance

Comments

@sheridancbio
Copy link
Collaborator

Done Condition (What do we need? Why do we need it? Keep this is small as possible!)

Technical Description (How are we going to achieve the above)

Our current approach for clearing the persistence caches involves restarting the instances/pods of redis holding the cache. This process take a couple of minutes and there is a service outage which is noticeable and causes 500 errors in attached cbioportal websites.
The proper location for this issue / scrum story needs to be determined. The responsibility for addressing this problem must be negotiated as well.

Potential Issues

Dependencies

Technical Requirements

Outside People/Teams

Changes

@sheridancbio sheridancbio added backend-scrum items centered around engineering activities bug Something isn't working Pipeline Maintenance labels Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend-scrum items centered around engineering activities bug Something isn't working Pipeline Maintenance
Projects
None yet
Development

No branches or pull requests

1 participant