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

Investigate if we can or cannot retry a getMore command after getting a StaleDbVersion in the shard

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 2

      When a StaleDbVersion, StaleConfig, or ShardCannotRefreshDueToLocksHeld exception is triggered in the Service Entry Point, a refresh is performed and the command is retried (code). 

      The decision to retry the command depends on certain conditions. For example, we cannot retry the command when executing a getMore, as the cursor may already be lost.  

      This retry policy only applies when the error from the original command is StaleConfig or ShardCannotRefreshDueToLocksHeld, and not StaleDbVersion.

      The goal of this ticket is to investigate if we can have a consistent retry approach for all three stale config exceptions for the getMore command.

            Assignee:
            Unassigned Unassigned
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: