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

Determine the errors on which MigrationSourceManager::commitDonateChunk doesn't need to do a chunk metadata refresh.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • Sharding 2016-10-10

    Description

      When ErrorCodes::BalancerLostDistributedLock is received, there's no need to refresh the chunk metadata to find out whether it's okay to fail the command normally or the shard must fassert because the state is unrecoverable.

      There may be other errors as well that the CommitChunkMigration command returns where it is assured the command can safely fail without any concern about corrupt metadata.

      Check out whether the RemoteCommandRetryScheduler::kAllRetriableErrors or RemoteCommandRetryScheduler::kNotMasterErrors sets of error codes can be used in some way.

      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: