Elasticsearch Ownership and Rollout
Context
See [BD 19-20] Technical Plan (Haystack Replacement, Elasticsearch Upgrade)
Runbook
Effort Coordination
This blended project upgrades our outdated and unsupported Elasticsearch from version 1.5 to version 7 in each of our services. We will need a resource from each owning squad to do a final review and deploy of the Elasticsearch upgrade for their owning service. The expected effort is:
Squad engineer’s review of PR: 2-5 hours depending on the complexity of the service’s use of Elasticsearch (PR will already be reviewed carefully by @Diana Huang or @Michael Terry (Deactivated))
Squad engineer’s deploy and monitoring of the migration: 2-3 days depending on production rollout
Service/Repo | Owning Team | PRs | Current Blocker | Status |
---|---|---|---|---|
terraform | Arch-BOM |
| @Tim McCormack working on updating ES clusters to ES 7.8. | |
devstack | SRE / Arch-BOM | https://github.com/edx/devstack/pull/611
|
|
|
SRE |
| indexing on prod caused errors due to malformed tags - checking to see if we can/should fix this. |
| |
Engage (Always Available) | - Merged and reverted on Stage. Waiting for new PR with original code + fixes. Fixes code: |
|
| |
TNL |
|
|
| |
TNL |
|
|
| |
Data Engineering |
| @Stuart Young (Deactivated) review and testing |
|