[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: |
|
||||||||||||||||
| 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: Fix receipient side. |
| Comment by Githook User [ 15/Dec/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Tighten locking policy for donor side of migration. |