Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • reliability reliability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,379
    • Issues 1,379
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Infrastructure TeamGitLab Infrastructure Team
  • reliabilityreliability
  • Issues
  • #4525
Closed (moved) (moved)
Open
Created Jul 04, 2018 by Stan Hu@stanhuMaintainer

2018-07-04 Increased sequential reads on projects table in 11.1 RC2

image

I noticed there were 3 post-deploy migrations that were still down:

  down    20180417102933  Drop repository storage events for geo events
  down    20180604123514  Cleanup stages position migration
  down    20180608150653  Add index to projects on repository storage last repository updated at

I've since applied those, and we are up to date.

I noticed this Geo query is timing out:

SELECT COUNT(*) FROM "projects" INNER JOIN "project_repository_states" ON "project_repository_states"."project_id" = "projects"."id" WHERE ("project_repository_states"."repository_verification_checksum" IS NOT NULL) AND "project_repository_states"."last_repository_verification_failure" IS NULL;

Which seems to be called via the Geo::MetricsUpdateService:

Geo::RepositoryVerificationFinder.new.count_verified_repositories`
Edited Jul 10, 2018 by John Jarvis
Assignee
Assign to
Time tracking