Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • scalability scalability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 270
    • Issues 270
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Infrastructure TeamGitLab Infrastructure Team
  • scalabilityscalability
  • Issues
  • #1131
Closed
Open
Issue created Jun 11, 2021 by Craig Miskell@cmiskellOwner

Remove the trace chunks migration flag

The migration capability implemented in #1095 (closed) needs to be either:

  1. Documented, for others to follow later, or
  2. Removed (the feature flag, basically).

This must be done before we can consider the Epic completed, but can be done as a cleanup (non-blocking on the actual migration)

Further Information

The migration code will be used by GitLab.com to perform this migration. Once the migration is completed, we (GitLab.com) won't need this code again. The only reason to leave it in place in the code base is if other large GitLab installations will need to perform the same migration.

The migration might be needed by installations where their CI trace chunks make up a large enough portion of redis-persistent traffic - for example, trace chunks are between 50% and 60% of our traffic.

Update 2021-06-18

We're going to go ahead with removing the migration code: #1131 (comment 605067774)

Edited Jun 18, 2021 by Bob Van Landuyt
Assignee
Assign to
Time tracking