Retry adding personal_namespace_id column to events (GitLab.com)
What does this MR do and why?
This is the second attempt the add a new column to events
that will be used a part of a composite sharding key.The first attempt was reverted because acquiring a lock on events
did not succeed - !164713 (comment 2090794956).
Here we add the column in a post-deployment migration for GitLab.com only, so that we have better control when the migration will be executed. Once we succeed there will be subsequent MR to add the column the regular way for all other instances (!165127 (comment 2092878736)).
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #462801