[SERVER-31933] Add prepareSnapshot method to avoid doing this implicitly in _getOptimes mutex Created: 13/Nov/17 Updated: 30/Oct/23 Resolved: 14/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Fixed | 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: | Storage 2017-11-13 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Instead of unconditionally establishing a snapshot right away when beginning a UnitOfWork, only do this when acquiring a new optime. This keeps the transaction lifetime as short as possible and should fix BF-7113, while still avoiding starting transactions inside of the _getNextOpTimes mutex. |
| Comments |
| Comment by Githook User [ 14/Nov/17 ] |
|
Author: {'name': 'Geert Bosch', 'username': 'GeertBosch', 'email': 'geert@mongodb.com'}Message: |