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

remove unnecessary check that RangeDeleter has run after removeShard in remove2.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.14
    • Fix Version/s: 3.4.0-rc1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2016-10-10

      Description

      The test removes a shard and tries to put it back again. However, it is possible that the migration cleanup task has not yet completed so attempting to re-add the shard will result to "local database exist in another shard" error.

      The test attempts to prevent this by checking the currOp for the cleanup task:
      https://github.com/mongodb/mongo/blob/r3.3.14/jstests/sharding/remove2.js#L26-L30

      But the issue here is that the balancer can run with

      { _waitForDelete: true }

      and this will mean that the cleanup will happen inline with moveChunk and the check above will not catch this.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: