Characterize and capture as an issue the persistence cache out-of-service problem #1453
Labels
backend-scrum
items centered around engineering activities
bug
Something isn't working
Pipeline Maintenance
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
The text was updated successfully, but these errors were encountered: