[SERVER-16322] Make sure that RecoveryUnit::commit() can safely throw WriteConflictException Created: 25/Nov/14 Updated: 19/Sep/15 Resolved: 31/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Igor Canadi | Assignee: | Geert Bosch |
| 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 | ||||||||
| Sprint: | Quint Iteration 7 | ||||||||
| Participants: | |||||||||
| Description |
|
Our first implementation of CC in RocksDB was to resolute conflicts in the commit() call. However, there are two things that didn't work: We're currently transitioning our CC implementation to check conflicts on write rather than commit. However, in the future we might want to transition back to commit-time-resolution. |
| Comments |
| Comment by Githook User [ 31/Jul/15 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: Map reduce did not handle WriteConflictExceptions at commit time well. |