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

Interrupting collMod can leave behind inconsistent collection options

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: 7.0.3, 6.0.12, 8.0.0-rc0
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • v8.0, v7.0, v6.0
    • CAR Team 2024-05-27

      Today, the collMod coordinator broadcasts `shardsvrCollModParticipant` to all shards in the cluster. The coordinator will parse each shard response depending if that shard owns any chunk.

      If we move an unsharded collection from its db primary shard, making that collection tracked and, behind the scenes, an unsplittable collection with one chunk placed in another shard, and we run a collMod, we may end up with inconsistent collection options.

      The collmod coordinator will target the shard that contains the only chunk - processing its successful response - and the db primary shard that contains locally the collection but without chunks - ignoring its error response.

      That is, we have created a collection options mismatch inconsistency.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: