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

In attachCursorToPipeline when local read fails we should not catch stale config exceptions

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • 113

      In attachCursorToPipeline we catch StaleDbVersion and StaleShardVersionError exceptions, but in theory we should not, as 
      sharding::router::CollectionRouter already handles this type of errors.

      But if we remove them, we just fail with "Exceeded maximum number of 10 retries attempting .. sharding status of collection ... is not currently known and needs to be recovered"
       
      This means that somewhere we don't handle config refresh correctly.

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            ivan.fefer@mongodb.com Ivan Fefer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: