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

Investigate non auto-retry commands on StaleConfig error

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23

      We have received recently some complaints about the non-retry behaviour on StaleConfig error when running a count command.

      When mongos receives a count command, it's sending out a scatter-gather request to all shards owning chunks. Since the scatter-gather utility is not retrying on StaleConfig errors, the StaleConfig error is being reported to the user. 

      After browsing the code, we have seen there are several commands using the same scatterGatherVersionedTargetByRoutingTable utility, so they are likely to don't reply on StaleConfig either.

      The aim of this ticket is to investigate more deeply which commands are not retrying on StaleConfig and to figure out how to solve this.

            silvia.surroca@mongodb.com Silvia Surroca
            silvia.surroca@mongodb.com Silvia Surroca
            0 Vote for this issue
            4 Start watching this issue