Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Query
Case:

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.

duplicates

SERVER-32307 Make AsyncResultsMerger kill sequence issue killCursors without waiting for outstanding batches

Closed

is related to

SERVER-31782 allow aggregation to take an 'allowPartialResults' option

Backlog

SERVER-6496 provide a way to kill a sharded query on all shards

Closed

related to

SERVER-3322 sharded aggregations should be very tolerant of node failures

Backlog

SERVER-17716 Correlate the parts of distributed ops in db.currentOp() output

Closed

Assignee:: Backlog - Query Team (Inactive)

Reporter:: Osmar Olivo

Participants:: Backlog - Query Team, Charlie Swanson, David Storch, Osmar Olivo

Votes:: 3 Vote for this issue

Watchers:: 15 Start watching this issue

Created:: Mar 23 2015 04:54:44 PM UTC

Updated:: Dec 06 2022 04:54:15 AM UTC

Resolved:: Apr 23 2018 08:51:32 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates