[SERVER-16432] Chunk migration data structures not properly synchronized with storage engines that offer document-level locking Created: 05/Dec/14  Updated: 24/Dec/14  Resolved: 18/Dec/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.8.0-rc2
Fix Version/s: 2.8.0-rc4

Type: Bug Priority: Blocker - P1
Reporter: Andy Schwerin Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16426 d_migrate getActive() mtx is very hot Closed
Related
related to SERVER-16540 Potential race in migration can have ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

The migrateFromStatus data structure is largely synchronized by the lock on the collection containing the chunk that is currently migrating. This implementation assumes that modifications of a collection exclusively lock that collection, which is no longer the case for document-level locking storage engines.



 Comments   
Comment by Githook User [ 18/Dec/14 ]

Author:

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

Message: SERVER-16432 Chunk migration data structures not properly synchronized

Fix receipient side.
Branch: master
https://github.com/mongodb/mongo/commit/50dc6dbe394c42d03659aa3410954f1e3ff46740

Comment by Githook User [ 15/Dec/14 ]

Author:

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

Message: SERVER-16432 Chunk migration data structures not properly synchronized

Tighten locking policy for donor side of migration.
Branch: master
https://github.com/mongodb/mongo/commit/ab70613187b0f2c1488a4fe6750b2f51da278afb

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