[SERVER-6834] jstests/sharding/read_pref.js fails sometimes Created: 23/Aug/12 Updated: 11/Jul/16 Resolved: 30/Aug/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.1, 2.3.0 |
| 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 | ||
| Environment: |
Failure seen in Windows x64 |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Buildbot sharding suite: http://buildlogs.mongodb.org/build/50345026d2a60f449d00091a/test/5034ade0d2a60f2e22000e7c/ jstests/sharding/read_pref.js stops 4 out of 5 nodes in a replica set, leaving just a secondary running. But it tests that it has reached this state by looking at the state of only one of the nodes that it has stopped (and the one it left running), so the test for 'readPref( "nearest" )' may try to use a secondary that has been stopped. The test should wait until mongos sees all stopped nodes as down before testing "nearest". |
| Comments |
| Comment by auto [ 12/Sep/12 ] |
|
Author: {u'date': u'2012-08-23T07:42:21-07:00', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Wait for all the nodes that we stopped to be seen as { ok : false }before proceeding to the next part of the test. |
| Comment by Tad Marshall [ 30/Aug/12 ] |
|
Backport to 2.2 branch would make the test reliable there. |
| Comment by auto [ 30/Aug/12 ] |
|
Author: {u'date': u'2012-08-23T07:42:21-07:00', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: Wait for all the nodes that we stopped to be seen as { ok : false }before proceeding to the next part of the test. |