[SERVER-6403] sharded indexes are queried via the db primary, which is not guaranteed to have the full set of collection indices Created: 11/Jul/12  Updated: 11/Jul/16  Resolved: 02/Aug/12

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: 2.0.6, 2.1.2
Fix Version/s: 2.2.0-rc1

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

Attachments: File shard_indexes.js    
Issue Links:
Depends
is depended on by SERVER-6342 indexes in sharding configuration Closed
Operating System: ALL
Participants:

 Description   

Because sharded indexes are created by sending "create index" ops to all shards containing the collection, and queries for indexes (getIndexes()) are fulfilled by checking the shard primary, it's possible for getIndexes() to not report correctly.



 Comments   
Comment by auto [ 02/Aug/12 ]

Author:

{u'date': u'2012-08-02T12:11:24-07:00', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}

Message: SERVER-6403 - handle some cases where a sharded collection has no chunks on primary for getting indexes
Branch: master
https://github.com/mongodb/mongo/commit/1a956a8214513ad827d059e88d6cba2948e03dfd

Comment by Greg Studer [ 11/Jul/12 ]

See attached ticket for more context.

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