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

New refine collection shard key might try to access invalid collection object

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.1.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v7.1
    • Sharding EMEA 2023-09-18
    • 161

      SERVER-76486 added a new refine collection shard key coordinator that is authoritative in shards, one of the changes include reducing the number of in-memory variables, to simplify how to maintain them synchronized with the persisted state. One of the changes was storing the collection UUID in the coordinator document, this should work for most of the scenarios, however, the interleaving described in SERVER-78997 might generate a situation where the collection object is trying to be accessed when it shouldn't.

      We should add an uassert that prevents that access.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: