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

Concurrent rename and shard collection causes shard collection to fail

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • ALL
    • 35

      While calling trying to check if there are any documents here, it can hit the ""Executor error during find command :: caused by :: collection dropped." error and fail the entire command. Drop and shardCollection on the same collection are not supposed to happen at the same time, but it is possible with renameCollection (since rename never takes dist lock) and dropTarget set to true.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: