Issues that should be solved before we can deploy Gitaly's transactions on production. The epic is split into three sub epics that are milestones on the journey to full production rollout: 1. https://gitlab.com/groups/gitlab-org/-/epics/14531+ - The rollout is still minimal, so we accept that we may manually fix problems on the canary nodes should something happen. We'll pursue this goal first to gather feedback and metrics faster. 2. https://gitlab.com/groups/gitlab-org/-/epics/14532+ - The rollout is wide, we no longer want to manually fix issues should anything happen. We'll have more preventative measures in place than we'll have for the canary deployment. We hope to discover any lingering issues before rolling out to self-managed and dedicated. 3. https://gitlab.com/groups/gitlab-org/-/epics/14533+ - At this point, things should be rock solid as we the rollout should be entirely hands off for administrators and dedicated. <!-- STATUS NOTE START --> ## Status 2025-09-23 The focus is still on the benchmarking tooling so we can get better results on how different kinds of workloads work with transactions, and how any tuning done affects the results. https://gitlab.com/gitlab-org/gitaly/-/issues/6732#note_2762963547 contains more details, but there's been two high level improvements to the tooling: - https://gitlab.com/gitlab-org/gitaly/-/merge_requests/8160+ - We can now run different configuration on different Gitaly nodes, including a different versions of Gitaly, and gather results to see the difference. - https://gitlab.com/gitlab-org/gitaly/-/merge_requests/8148+ - We can now visualize results by parsing Gitaly's logs. _Copied from https://gitlab.com/groups/gitlab-org/-/epics/13306#note_2769924226_ <!-- STATUS NOTE END -->