[SERVER-22453] Fix race condition in donor_shard_abort_and_start_new_migration.js Created: 03/Feb/16  Updated: 18/Nov/16  Resolved: 04/Feb/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.2.3, 3.3.2

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Sharding 10 (02/19/16)
Participants:
Linked BF Score: 0

 Description   

donor_shard_abort_and_start_new_migration.js has a race between aborting the first migration and starting the second migration.



 Comments   
Comment by Ian Whalen (Inactive) [ 04/Feb/16 ]

Are we certain this was actually fixed in master by d0ae5688ea3083d2916c2213a262ed0ec2cf6b4f? It still appears to be failing:

https://evergreen.mongodb.com/task_history/mongodb-mongo-master/sharding_WT?revision=1335e35ce45539192475dddb1c82557f5d36d028#/donor_shard_abort_and_start_new_migration.js=fail

Comment by Githook User [ 04/Feb/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-22453 Fixing race condition in donor_shard_abort_and_start_new_migration.js between aborting first migration and starting second migration.
Branch: master
https://github.com/mongodb/mongo/commit/11fe3dafabdaba6c346aef794b50e4be7285e922

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