[SERVER-20918] MigrationSourceManager::done called twice Created: 14/Oct/15  Updated: 25/Jan/17  Resolved: 22/Oct/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.1.9
Fix Version/s: 3.2.0-rc1

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding B (10/30/15)
Participants:

 Description   

One is in the destructor of the statusHolder:

https://github.com/mongodb/mongo/blob/r3.1.9/src/mongo/db/s/move_chunk_command.cpp#L83

and the other is when the critical section finishes:

https://github.com/mongodb/mongo/blob/r3.1.9/src/mongo/db/s/move_chunk_command.cpp#L511

This creates a small window where a new migration can start and the destructor will set the state of the migration to not active.



 Comments   
Comment by Githook User [ 22/Oct/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-20918 Remove redundant OperationContext parameter in ChunkMoveOperationState
Branch: master
https://github.com/mongodb/mongo/commit/67b215a1a74743b5296c37d8c3bcb73fa57c54df

Comment by Githook User [ 22/Oct/15 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-20918 MigrationSourceManager::done called twice
Branch: master
https://github.com/mongodb/mongo/commit/289b15c027610bf607007dc0a47a2b02d1051506

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