TranslatorSRI / NodeNormalization

Service that produces Translator compliant nodes given a curie
MIT License
10 stars 6 forks source link

Propose to ITRB that we use rolling Serverless ElastiCache Redis #252

Closed gaurav closed 4 months ago

gaurav commented 8 months ago

The idea is that our process for future NodeNorm upgrades should be:

  1. [RENCI] Upload NodeNorm Redis RDB files to S3
  2. [ITRB] Create new Serverless Redis RDB servers by restoring them from the S3 RDB files
  3. [RENCI] Test Serverless servers, confirm that they are correctly loaded
  4. [RENCI] Update Helm chart for nn-web with hostnames and passwords for the new Serverless Redis RDB servers
  5. [ITRB] Redeploy nn-web with the new servers.
    • IF deployment fails: deploy previous version of the code and wait for updates
      1. [ITRB] Delete old Serverless Redis RDB servers
      2. [ITRB] Make database backups of the Serverless Redis RDB servers

We need to:

gaurav commented 4 months ago

A back-of-the-envelope calculation suggests that this will be more expensive than the per-node we're currently playing for. A better option for us is Data tiering, which offloads some of the database onto an SSD, which we have tried successfully on ITRB. Closing this as something we want to try to investigate.