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

Step downs while sharding a collection in mixed binaries shards might crash the old binary

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.2, 6.0.0-rc0, 5.0.7
    • Affects Version/s: 5.0.5, 5.3.0-rc3
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • ALL
    • v5.3, v5.2, v5.0
    • Sharding EMEA 2022-03-21
    • 162

      In the create collection coordinator documents we have strict as true, considering we have the create collection request parameters as fields in the document, after SERVER-62454 and SERVER-63732 we've added 3 new parameters to the request, making the coordinator document in new versions incompatible with old ones.

      The crash scenario is the following: if we have a mixed binaries shard and a shard collection is issued against the primary node in 6.0 or 5.3 and then a stepdown happens, if the new primary is 5.0 then the parse of the document will fail, making the construction to throw, which in turn will hit the DDL coordinator construction invariant. We should set strict false in the create collection coordinator document.

            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            0 Vote for this issue
            3 Start watching this issue