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

Terminate sharded queries immediately after a failure

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None

      Description

      If a sharded query incurs a failure (such as a dead cursor) on any one shard, when that error is returned to the mongos, mongos should terminate the query on the remaining shards automatically.

      Otherwise, we will continue utilize processing power and time on a query we already know is going to fail. This is particularly an issue if you have many long running cpu intensive queries, such as for analytics. I would like a failed query to be cleaned up across the cluster as fast as possible, or within some reasonable timeout, in order to free up resources more quickly for other queries.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-query Backlog - Query Team
              Reporter:
              osmar.olivo Osmar Olivo
              Participants:
              Votes:
              3 Vote for this issue
              Watchers:
              15 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: