Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 55.4k
    • Issues 55.4k
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1.6k
    • Merge requests 1.6k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • 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
  • #6481
Closed
Open
Issue created Jun 18, 2018 by Nick Thomas@nick.thomas🆓Contributor

Remove Ruby elasticsearch repository indexer

Currently, GitLab's Elasticsearch integration has two repository indexers:

  • Go (experimental, fast)
  • Ruby (stable, slow)

Maintaining two indexers is additional maintenance work, especially with large changes like gitaly#760 (closed) in the works.

We should commit to removing the Ruby elasticsearch indexer. The Go one has been around for over a year, and it has successfully indexed a significant proportion of projects on GitLab.com in the past with only a few bugs showing up: https://gitlab.com/gitlab-org/gitlab-elasticsearch-indexer/issues

We can resolve those issues before or after making the Go indexer the only choice; I don't have a strong opinion.

/cc @jacobvosmaer-gitlab @tommy.morgan @smcgivern @victorwu @mdelaossa @vsizov

Assignee
Assign to
Time tracking