Include per-shard info in mongos error response for scatter-gather find failures

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, when a scatter-gather find fails because one or more shards reject with IngressRequestRateLimitExceeded, the mongos error response is a flat top-level error with no per-shard information. establishCursors() throws the first shard error directly, with no raw field.

      Administrative/DDL commands already use appendRawResponses() to include per-shard results keyed by shard. It would be useful to have similar information for find failures, so clients and tests can identify which shard(s) caused the failure.

      Raised during review of SERVER-127629.

            Assignee:
            Anja Kalaba
            Reporter:
            Anja Kalaba
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: