Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,070
    • Issues 36,070
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,299
    • Merge Requests 1,299
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Merge Requests
  • !34069

Merged
Created Jun 08, 2020 by Dmitry Gruzd@dgruzdDeveloper0 of 13 tasks completed0/13 tasks

Add cluster reindexing feature to our ES integration

  • Overview 123
  • Commits 9
  • Pipelines 84
  • Changes 16

What does this MR do?

This MR automates steps for the cluster reindexing process gitlab-com/gl-infra/production#2213 (closed)

To schedule a reindexing job you will need to run rake gitlab:elastic:reindex_cluster which will create a ReindexingTask record.

ElasticClusterReindexingCronWorker runs every minute and executes a job with in_progress flag. We can only have 1 job with this flag since we have a unique index.

#213629 (closed)

Reindexing logic/stages

After we create a ReindexingTask it has initial stage

  • initial stage is needed to complete initial checks (i.e. storage requirements) and to enable indexing pause feature. We expect a delay between stages to be enough for existing indexing requests to complete.
  • reindexing stage creates a new index and triggers Elasticsearch reindex API
  • in_progress stage is the polling stage, we're waiting for the task to complete
  • As final stages we have success and failure

Stages graph visualisation

Screenshot_2020-06-29_at_13.09.20

Database changes

This MR introduces a table called reindexing_tasks and ReindexingTask model

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

Closes #213629 (closed)

Edited Sep 28, 2020 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Reviewer
Request review from
13.2
Milestone
13.2 (Past due)
Assign milestone
Time tracking
Reference: gitlab-org/gitlab!34069
Source branch: 213629-cluster-reindexing-feature