Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,331
    • Merge requests 1,331
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #345207
Closed
Open
Issue created Nov 09, 2021 by Nick Nguyen@nhxnguyenDeveloper0 of 2 checklist items completed0/2 checklist items

Deprecate `gitlab-ctl promote-to-primary-node` and `gitlab-ctl promote-db`

Deprecation Summary

With the introduction of a single-command to promote a secondary node, gitlab-ctl geo promote will replace the previous promotion commands gitlab-ctl promote-to-primary-node and gitlab-ctl promoted-db.

Beginning in 14.5, the previous promotion commands will be deprecated.

In 15.0, we will remove the commands gitlab-ctl promote-to-primary-node and gitlab-ctl promoted-db.

Breaking Change

In 15.0, administrators can no longer use the deprecated commands and will need to use gitlab-ctl geo promote to perform a failover. We recommend that, before upgrading to 15.0, administrators test the new gitlab-ctl promote command and incorporate it into their failover processes.

Affected Topology

This affects self-hosted customers who use Geo for Disaster Recovery.

Affected Tier

Premium and Ultimate

Checklist

  • @mention your stage's stable counterparts on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.

    • To see who the stable counterparts are for a product team visit product categories
      • If there is no stable counterpart listed for Sales/CS please mention @timtams
      • If there is no stable counterpart listed for Support please @mention @gitlab-com/support/managers
      • If there is no stable counterpart listed for Marketing please mention @williamchia
  • @mention your GPM so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

14.5

Planned Removal Milestone

15.0

Links

Edited Nov 11, 2021 by Nick Nguyen
Assignee
Assign to
Time tracking