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

Renaming a sharded collection might hang if the destination collection is previously dropped

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • ALL
    • Sharding EMEA 2021-08-23, Sharding EMEA 2021-09-06
    • 140

    Description

      When renaming a sharded collection, there is a phase where the CRUD operations are reactivated on all the involved shards, and this is done by sending a command, however, a previous drop of the destination collection might generate an scenario where the next refresh on the recipient fails with a "QueryPlanKilled" error, and because there is a retry policy implemented, the command does not terminate. We could prevent the error like it is done on the first phase or checking for QueryPlanKilled errors specifically.

      Attachments

        Activity

          People

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: