Skip to content

[Minor Version] Upgrade Global Search Elasticsearch cluster to 8.11.4

Production Change

Change Summary

The Global Search Elasticsearch cluster gprd-indexing-20220523 will be upgraded to Elasticsearch version 8.11.4 from 8.6.2. The staging cluster gstg-indexing-20220519 will be upgraded first to verify.

Change Details

  1. Services Impacted - ServiceSearch
  2. Change Technician - @maddievn
  3. Change Reviewer - @terrichu
  4. Time tracking - 120 minutes (changes) + 360 minutes (rollback)
  5. Downtime Component - No downtime required for minor (rolling upgrade) or major (blue/green deployment) version upgrades.
  6. Scheduled time - Friday, 12 April at 7:00 UTC. We have coverage in APAC, EMEA and AMER.

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 4 hours

Phase 0: Pre-flight

Phase 1: Monitoring cluster Upgrade

  • In the Elastic Cloud UI, create a snapshot
  • In the Elastic Cloud UI, click Upgrade for the deployment
  • Select the version, click the Upgrade button
  • Check that metrics/logs are still being sent to the cluster for the indexing and logs clusters

Phase 2: Staging Upgrade

Minor version upgrades

  • In the Elastic Cloud UI, create a snapshot
  • In the Elastic Cloud UI, click Upgrade for the deployment
  • Select the version, click the Upgrade button
  • Test read code paths
    • Code
    • Notes
  • Test write code paths
    • Code
    • Notes

Phase 3: Production Upgrade

Minor version upgrades

  • In the Elastic Cloud UI, create snapshot
  • In the Elastic Cloud UI, click Upgrade for the deployment
  • Select the version, click the Upgrade button
  • Test read code paths
    • Code
    • Notes
  • Test write code paths
    • Code
    • Notes

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

** Minor upgrades **

Estimated Time to Complete (mins) - 30-120 minutes (depending on how long the upgrade took and how much data needed to be restored)

Monitoring

Key metrics to observe

sidekiq

Performance

Elastic Cloud

Change Reviewer checklist

C4 C3 C2 C1:

  • Check if the following applies:
    • The scheduled day and time of execution of the change is appropriate.
    • The change plan is technically accurate.
    • The change plan includes estimated timing values based on previous testing.
    • The change plan includes a viable rollback plan.
    • The specified metrics/monitoring dashboards provide sufficient visibility for the change.

C2 C1:

  • Check if the following applies:
    • The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
    • The change plan includes success measures for all steps/milestones during the execution.
    • The change adequately minimizes risk within the environment/service.
    • The performance implications of executing the change are well-understood and documented.
    • The specified metrics/monitoring dashboards provide sufficient visibility for the change.
      • If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
    • The change has a primary and secondary SRE with knowledge of the details available during the change window.
    • The labels blocks deployments and/or blocks feature-flags are applied as necessary

Change Technician checklist

  • Check if all items below are complete:
    • The change plan is technically accurate.
    • This Change Issue is linked to the appropriate Issue and/or Epic
    • Change has been tested in staging and results noted in a comment on this issue.
    • A dry-run has been conducted and results noted in a comment on this issue.
    • For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
    • Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
    • There are currently no active incidents that are severity1 or severity2
    • If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.
Edited by Terri Chu