[SERVER-10574] shard_kill_and_pooling.js failing intermittently in MCI on linux 64 Created: 15/Aug/13 Updated: 11/Jul/16 Resolved: 26/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | sam.helman@10gen.com | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux-64 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Failure on MCI: Same run passed on buildbot: http://buildlogs.mongodb.org/Linux%2064-bit/builds/5724/test/sharding/shard_kill_and_pooling.js Talked to Greg, he thinks it may be related to timing and the sharding test itself. |
| Comments |
| Comment by auto [ 26/Aug/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Greg Studer [ 19/Aug/13 ] |
|
Issue is we need to be sure writes are flushed to disk before hard-killing the mongod (done on purpose in this test). GLE isn't enough here. |