enable gitaly info/refs caching using the gitaly_inforef_uploadpack_cache feature flag
C4
Production Change - Criticality 4Change Objective | Describe the objective of the change |
---|---|
Change Type | ConfigurationChange |
Services Impacted | Gitaly |
Change Team Members | @mwasilewski-gitlab @zj-gitlab |
Change Severity | C4 |
Change Reviewer or tested in staging | A colleague who will review the change |
Dry-run output | - |
Due Date | 2019-11-11 09:09:00 UTC |
Time tracking |
Detailed steps for the change. For each step the following must be considered:
- pre-conditions for execution of the step - how to verify it is safe to proceed
- execution commands for the step - what to do
- post-execution validation for the step - how to verify the step succeeded
It is strongly recommended to:
- Note relevant graphs in grafana to monitor the effect of the change, including how to identify that it has worked, or has caused undue negative effects
- Review alerts that may go off that can be silenced pro-actively
Rollback steps
- As for the original steps. It may be acceptable to reference the change steps as the process, with variations (e.g. Revert commit and run deployment).
- It is acceptable to list a full rollback process, and allow for the applier to select where to start based on how far through they got.
created this issue for future reference (how to enable/disable inforef caching)
/chatops run feature set gitaly_inforef_uploadpack_cache true