[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:

https://mci.10gen.com/ui/task/mongodb_mongo_master_linux_64_c9b019d326dca25c7f88abb5b74aef2476b69aec_13_08_15_03_45_06_sharding_linux_64

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: SERVER-10574 shard_kill_and_pooling.js make sure we're flushed to disk before unclean shutdown
Branch: master
https://github.com/mongodb/mongo/commit/6a6bc2da6536ebf4a4c2faae99f1963cd8772f87

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.

Generated at Thu Feb 08 03:23:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.