[SERVER-4887] sharded queries on system.indexes hit the primary Created: 06/Feb/12  Updated: 11/Jul/16  Resolved: 06/Mar/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.6.0-rc0

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-11982 connection error when doing sharded c... Closed
Operating System: ALL
Participants:

 Description   

... they should really hit all shards, or at least a single shard on which the collection is sure to exist. Also, we don't seem to have a standard way of detecting/displaying via mongos when indexes are different between shards.=



 Comments   
Comment by Greg Studer [ 06/Mar/14 ]

Fixed as part of SERVER-11982.

Generated at Thu Feb 08 03:07:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.