Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 39,511
    • Issues 39,511
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,222
    • Merge requests 1,222
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Merge requests
  • !28369

You need to sign in or sign up before continuing.
Merged
Created Mar 30, 2020 by John Cai@johncaiContributor5 of 5 tasks completed5/5 tasks

Add Praefect rake task to print out replica checksums

  • Overview 58
  • Commits 1
  • Pipelines 25
  • Changes 3

What does this MR do?

Related to: #35758 (closed)

When praefect is being used, the administrator needs to be able to know whether or not a given project's repository has the same checksum across its replicas.

it is invoked by:

## by project id
bundle exec rake "gitlab:praefect:replicas[1]"

the output looks like the following:

| project_name | praefect-internal-0 (primary)            | praefect-internal-1                      | praefect-internal-2                      |
-------------------------------------------------------------------------------------------------------------------------------------------------
| test1        | 3f9fe54e92ea1e86bc4af841d8b93dacd788aaeb | 343a4d2e1b1a30dd91e6cc5abebfc7ebc2f0cc93 | 343a4d2e1b1a30dd91e6cc5abebfc7ebc2f0cc93 |
| helllohello  | c5d87c321e349d039d69b8be4d4c4e26cf1b1fd6 | c5d87c321e349d039d69b8be4d4c4e26cf1b1fd6 | c5d87c321e349d039d69b8be4d4c4e26cf1b1fd6 |

Screenshots

Does this MR meet the acceptance criteria?

Conformity

  • Changelog entry
  • [-] Documentation (if required)
  • Code review guidelines
  • Merge request performance guidelines
  • Style guides
  • [-] Database guides
  • [-] Separation of EE specific content

Availability and Testing

  • Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
  • [-] Tested in all supported browsers
  • [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • [-] Security reports checked/validated by a reviewer from the AppSec team
Edited Apr 09, 2020 by Mayra Cabrera
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: jc-replicas-rake

Enable Gitpod?

To use Gitpod you must first enable the feature in the integrations section of your user preferences.

Cancel Enable Gitpod