[SERVER-8668] jstests/sharding/mrShardedOutput.js needs an index Created: 22/Feb/13 Updated: 11/Jul/16 Resolved: 27/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The test does a non-indexed search for each of 200,000 documents across a shared collection in one of its later steps and the test sometimes times out (the overall test takes over 3 hours). The goal is to make sure that all 200,000 documents exist, not to exercise non-indexed search, so these failures are spurious for the purpose of the test. Adding an index on the search field should eliminate the timeouts. The latest example: |
| Comments |
| Comment by auto [ 27/Feb/13 ] |
|
Author: {u'date': u'2013-02-27T18:50:20Z', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: Add an index on the "i" (document number) field to make lookups for possibly |
| Comment by Tad Marshall [ 27/Feb/13 ] |
|
Looking at the test again and studying the logs, it seems that the effect of an index would be to make the test's failures be reported correctly rather than timing out. The code that would benefit from the index is only run when the test is going to fail anyway (the code block ends with an "assert(false)") so these failures are causing bad reporting; they are not the "cause" of any failures. |
| Comment by Tad Marshall [ 22/Feb/13 ] |
|
Another one: |