[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: |
|
||||||||
| Issue Links: |
|
||||||||
| 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: |
| Comment by Greg Studer [ 11/Jul/12 ] |
|
See attached ticket for more context. |