Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-26166

CommitChunkMigration command should commit chunk even if it's been split.

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • Fully Compatible

    Description

      Since a migration can potentially run without a distributed lock if the balancer restarts and abandons its active migration, there's a possibility – though slim – that a split occurs on the chunk that is moving and then the migration tries to commit.

      If the balancer holds the distlock again, and the collection version epoch still matches, the commit command then looks for the chunk in the config.chunks collection.

      It currently looks for an exact match, but this could be changed to allow for splitting.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: