2023-12-11 - Reindex all Zoekt-enabled namespaces in 2 phases
Production Change
Change Summary
This CR re-indexes the namespaces we've added as part of #17203 (closed) because it turned out that we've hit timeouts during the reindexing process and never completed indexing (see gitlab-org/cloud-native/charts/gitlab-zoekt#17 (closed)).
During the second phase we trigger reindexing for other namespaces to fix memory consumption creep.
Change Details
- Services Impacted - ServiceZoekt
- Change Technician - @dgruzd
- Change Reviewer - @terrichu
- Time tracking - 16h
- Downtime Component - No downtime
Set Maintenance Mode in GitLab
If your change involves scheduled maintenance, add a step to set and unset maintenance mode per our runbooks. This will make sure SLA calculations adjust for the maintenance period.
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - 500
-
Set label changein-progress /label ~change::in-progress
-
Post Zoekt memory and mmap graphs as a comment on the issue -
Execute the script on GPRD -
Perform Stage 1 namespace_ids = [6916923, 5942816, 630498, 56524891] reindex(max_delay_per_project: 10.seconds, dry_run: false, zoekt_indexed_namespaces: Zoekt::IndexedNamespace.where(namespace_id: namespace_ids))
-
Note the expected completion time as a comment on this issue -
Wait until it's completed -
Post Zoekt memory and mmap graphs as a comment on the issue
-
Perform Stage 2 of the CR namespace_ids = [6916923, 5942816, 630498, 56524891] reindex(max_delay_per_project: 10.seconds, dry_run: false, zoekt_indexed_namespaces: Zoekt::IndexedNamespace.where.not(namespace_id: namespace_ids))
-
Note the expected completion time as a comment on this issue -
You don't need to wait until it's completed. Reindexing can happen in the background
-
Set label changecomplete /label ~change::complete
-
Post Zoekt memory and mmap graphs as a comment on the issue
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete (mins) - 1
-
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
- Metric: Kibana logs for
Zoekt::IndexerWorker
- Location: https://log.gprd.gitlab.net/app/r/s/iaBgU
- What changes to this metric should prompt a rollback: Repeated failures to index projects
- Metric: Kibana dashboard for
Zoekt::IndexerWorker
- Location: https://log.gprd.gitlab.net/app/r/s/dvbCP
- What changes to this metric should prompt a rollback: Repeated failures to index projects
Change Reviewer checklist
-
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.
-
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 change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval.
- 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.
- The change execution window respects the Production Change Lock periods.
- For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
- 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.) - For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
- For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
- Release managers have been informed prior to any C1, C2, or blocks deployments 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 Dmitry Gruzd