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

Concurrent index build and rename over sharded collections may disrupt CRUD operations

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • 5.3.0-rc0, 5.0.5, 5.2.1
    • Sharding
    • None
    • Catalog and Routing
    • ALL

    Description

      Provided that it should not be common to build an index over a sharded collection while the latter is being renamed, it is technically possible to do so.

      The check for concurrent index builds happens in the local catalog rename code, called by rename participants after blocking CRUDs. If the two operations overlap, an assertion is thrown and the participant indefinitely retries the rename operation as long as the build is not finished.

      As a consequence, if an index build happens during a rename it is possible that CRUDs are blocked during the whole time of the build.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: