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

Do not assume that the collection is always sharded in ShardServerProcessInterface::checkRoutingInfoEpochOrThrow method

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.2, 5.1.0-rc0
    • Affects Version/s: 5.0.0-rc8
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-07-26
    • 145

      This code currently assumes that the collection is always sharded. When that's not the case, it ends up calling the ChunkManager::getVersion method that wasn't designed to be called over unsharded collections.

            Assignee:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Reporter:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: