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

Handle collection sharding state change during _clusterQueryWithoutShardKey

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • None
    • None
    • Sharding NYC
    • Fully Compatible
    • Sharding NYC 2023-02-20, Sharding NYC 2023-03-06, Sharding NYC 2023-03-20, Sharding NYC 2023-04-03, Sharding NYC 2023-04-17, Sharding NYC 2023-05-01, Sharding NYC 2023-05-15

    Description

      It's possible that maybe the routing table gets flushed or becomes stale through move chunks or a drop collection, which could cause the chunk manager on the clusterQueryWithoutShardKey to return NamespaceNotFound.

      In the case where a collection is dropped before the command is run, uasserting InvalidOptions when checking if the collection is sharded may prevent retrying on StaleConfig exceptions. It may be necessary to adjust the error handling here.

      Attachments

        Activity

          People

            sanika.phanse@mongodb.com Sanika Phanse (Inactive)
            jason.zhang@mongodb.com Jason Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: