Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
  • gitlab-ce
  • spec
  • lib
  • gitlab
  • database_spec.rb
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Fix intermittent merge errors due to replication lag · 9046a766
    Stan Hu authored Oct 05, 2020
    https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42435 attempted to
    fix the problem, but it did not work because EE databaase load balancing
    is not enabled in Sidekiq. Since it is disabled, the load balancer code
    would never post the write location to Redis, so the code for checking
    whether to stick to the primary was not able to be used.
    
    Since Sidekiq always uses the primary we can just use the main
    ActiveRecord connection to get the same information. We only post the
    write location if load balancing is configured.
    
    Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/247857
    9046a766
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7