[SERVER-26414] Don't preemptively abort test due to perceived machine slowness in migrateBig_balancer.js Created: 30/Sep/16  Updated: 25/Jan/17  Resolved: 30/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.4.0-rc0

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-10-10
Participants:
Linked BF Score: 0

 Description   

migrateBig_balancer.js runs the 'ping' command directly against the shards, and if that fails with a network error, assumes that that means the machine is having i/o problems and aborts the test. But aborting the test early doesn't really accomplish anything, as the test will still show up as failed in evergreen and has to be looked at, plus a single network disconnect does not necessarily mean there are serious i/o issues going on on the test machine. Instead of failing preemptively, the test should just run as normal and if there are i/o issues wait for the test to time out doing something, as all our other jstests do.



 Comments   
Comment by Githook User [ 30/Sep/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-26414 Don't preemptively abort test due to perceived machine slowness in migrateBig_balancer.js
Branch: master
https://github.com/mongodb/mongo/commit/ba344084775139e211e6d8904a2282c1cec1ad83

Generated at Thu Feb 08 04:12:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.