[SERVER-11132] "table scans not allowed" during parallel/basicPlus.js on RHEL 5.7 Created: 11/Oct/13 Updated: 11/Jul/16 Resolved: 11/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Kangas | Assignee: | hari.khalsa@10gen.com |
| 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 |
|
Hari, I saw you made a similar fix today in b2ee3b5, maybe missed one test? c1ab952e098b RHEL 5.7 64-bit parallel
|
| Comments |
| Comment by auto [ 11/Oct/13 ] | |||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'kangas', u'name': u'Matt Kangas', u'email': u'matt.kangas@mongodb.com'}Message: | |||||||||||||||||||||||||||||||||||||||||
| Comment by auto [ 11/Oct/13 ] | |||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'kangas', u'name': u'Matt Kangas', u'email': u'matt.kangas@mongodb.com'}Message: | |||||||||||||||||||||||||||||||||||||||||
| Comment by hari.khalsa@10gen.com [ 11/Oct/13 ] | |||||||||||||||||||||||||||||||||||||||||
|
Yes geo_update_btree2.js is the issue. Probably best to skip for parallel until we do a 2d cleanup sweep. | |||||||||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 11/Oct/13 ] | |||||||||||||||||||||||||||||||||||||||||
|
Oh, you mean geo_update_btree2.js which ran concurrent with the test that failed? In that case, agreed, we have to skip it for parallel or trash it. | |||||||||||||||||||||||||||||||||||||||||
| Comment by hari.khalsa@10gen.com [ 11/Oct/13 ] | |||||||||||||||||||||||||||||||||||||||||
|
kangas The geo test won't run correctly unless we disable table scans. It just happened to run before but it's a bad test that happens to work because of unreasonable assumptions about isolation etc. Either we should take it out of parallel or we should nix the test. | |||||||||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 11/Oct/13 ] | |||||||||||||||||||||||||||||||||||||||||
|
The test that failed was "S2 Test : jstests/exists8.js". Tests on that worker preceding it...
|