Rollout of `ci_current_partition_value_101`
Production Change
Change Summary
Tracking issue for enabling the feature flag for gitlab-org/gitlab#431461
With this feature flag we stop writing to ci_builds
and ci_builds_metadata
. The new records will be persisted into new partitions, stopping the growth of those tables. The data is readable regardless of the partition value or the flag state.
This was enabled on staging more than 2 weeks ago.
Change Details
- Services Impacted - ServiceGitLab Rails ServicePostgres
-
Change Technician -
@mbobin
-
Change Reviewer -
@morefice
- Time tracking - Time, in minutes, needed to execute all change steps, including rollback
- 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) - Estimated Time to Complete in Minutes
-
Set label changein-progress /label ~change::in-progress
-
/chatops run feature set --project=gitlab-com/www-gitlab-com ci_current_partition_value_101 true
-
wait a day -
/chatops run feature set --project=gitlab-org/gitlab ci_current_partition_value_101 true
-
wait a day -
/chatops run feature set ci_current_partition_value_101 5 --actors
-
wait 30 minutes -
/chatops run feature set ci_current_partition_value_101 10 --actors
-
wait 30 minutes -
/chatops run feature set ci_current_partition_value_101 25 --actors
-
wait 30 minutes -
/chatops run feature set ci_current_partition_value_101 50 --actors
-
wait 30 minutes -
/chatops run feature set ci_current_partition_value_101 true
-
Set label changecomplete /label ~change::complete
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes
-
/chatops run feature set ci_current_partition_value_101 false
-
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
- Metric: API error rates
- Location: https://dashboards.gitlab.net/d/stage-groups-pipeline_execution/e8b8feb9-4384-5fd6-8b99-b1008cd89642?orgId=1&viewPanel=25
- What changes to this metric should prompt a rollback: significant increase
- Metric: WEB error rates
- Location: https://dashboards.gitlab.net/d/stage-groups-pipeline_execution/e8b8feb9-4384-5fd6-8b99-b1008cd89642?orgId=1&viewPanel=26
- What changes to this metric should prompt a rollback: significant increase
- Metric: Sidekiq error rates
- Location: https://dashboards.gitlab.net/d/stage-groups-pipeline_execution/e8b8feb9-4384-5fd6-8b99-b1008cd89642?orgId=1&viewPanel=41
- What changes to this metric should prompt a rollback: significant increase
- Metric: New sentry errors
- Location: https://new-sentry.gitlab.net/organizations/gitlab/issues/?environment=gprd&project=3&statsPeriod=1h
- What changes to this metric should prompt a rollback: new errors related to the change
- Metric: Total Time in Queries per Node
- Location: https://dashboards.gitlab.net/d/patroni-ci-main/patroni-ci3a-overview?orgId=1&viewPanel=103
- What changes to this metric should prompt a rollback: significant increase
- Metric: Time in Transaction per Server
- Location: https://dashboards.gitlab.net/d/patroni-ci-main/patroni-ci3a-overview?orgId=1&viewPanel=105
- What changes to this metric should prompt a rollback: significant increase
- Metric: Tuple inserts per table
- Location: thanos
- What changes to this metric should prompt a rollback:
ci_builds_101
andci_builds_metadata_101
don't pick up theci_builds
andci_builds_metadata
rates
- Metric: Tuple updates per table
- Location: thanos
- What changes to this metric should prompt a rollback:
ci_builds_101
andci_builds_metadata_101
don't pick up theci_builds
andci_builds_metadata
rates
- Metric: Tuple deletes per table
- Location: thanos
- What changes to this metric should prompt a rollback: nothing,
ci_builds
should observe deletes as normal
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 Marius Bobin