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

removeShard needs to take into account asynchronous document deletion after migrate

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • ALL

    Description

      A shard may be removed by mongos, but open cursors may remain on the final migration's data waiting to be deleted. So long as these cursors are open, the data will not be deleted and the shard cannot be re-added. Need to also verify that all databases will be removed in this case.

      We should probably check for this case explicitly and check that the shard's sharded databases are removed before removing the shard. (Say that 5 times fast)

      Attachments

        Activity

          People

            Unassigned Unassigned
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: