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.

Sign up for GitHub

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

Jump to bottom

Redis 7.x upgrade #3382

Closed
2 of 3 tasks
AetherUnbound opened this issue Nov 21, 2023 · 1 comment
Closed
2 of 3 tasks

Redis 7.x upgrade #3382

AetherUnbound opened this issue Nov 21, 2023 · 1 comment
Assignees
@dhruvkb
Labels
💻 aspect: code Concerns the software code in the repository 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟧 priority: high Stalls work on the project or its dependents 🧭 project: thread An issue used to track a project and its progress 🧱 stack: api Related to the Django API 🧱 stack: infra Related to the Terraform config and other infrastructure

Comments

@AetherUnbound
Copy link
Contributor

AetherUnbound commented Nov 21, 2023 •
edited by dhruvkb

Start Date ETA Project Lead Actual Ship Date
2023-11-21 YYYY-MM-DD TBD TBD

Description

Our Redis clusters are currently two versions behind, and need to be upgraded to the latest version since 5.x is EOL.

Documents

  • Implementation Plan(s)

Issues

Prior Art
@AetherUnbound AetherUnbound added 💻 aspect: code Concerns the software code in the repository 🟧 priority: high Stalls work on the project or its dependents 🧭 project: thread An issue used to track a project and its progress 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🧱 stack: api Related to the Django API 🧱 stack: infra Related to the Terraform config and other infrastructure labels Nov 21, 2023
@AetherUnbound AetherUnbound mentioned this issue Nov 21, 2023
Closed
@dhruvkb
Copy link
Member

dhruvkb commented Jan 4, 2024

Redis has been upgraded to v7.1 in both staging and production. This is the latest version available through AWS Elasticache.

The approach we took was to make the API capable of working (even if the performance is a bit degraded) when Redis is inaccessible (#3505) and then upgraded Redis using the AWS management console UI. We monitored user endpoints through a k6 script (#3575). For most of the migration, Redis stayed available for reads and writes and the switchover did not cause any spikes in 5xx errors. Then the infrastructure resource was updated to match the values of the actual Elasticache instance (https://github.com/WordPress/openverse-infrastructure/pull/739).

@dhruvkb dhruvkb closed this as completed Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dhruvkb dhruvkb

Labels
💻 aspect: code Concerns the software code in the repository 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟧 priority: high Stalls work on the project or its dependents 🧭 project: thread An issue used to track a project and its progress 🧱 stack: api Related to the Django API 🧱 stack: infra Related to the Terraform config and other infrastructure
Projects
Openverse Project Tracker
Status: ✅ Success
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AetherUnbound @dhruvkb