[SERVER-46698] Invariant that operations which are holding open an oplog hole cannot call blocking functions Created: 06/Mar/20 Updated: 29/Oct/23 Resolved: 12/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | James Heppenstall |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution Team 2020-05-18 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This is a theoretical class of liveness bugs where operations cannot be replicated if a recovery unit with its commit timestamp set is prevented from committing/aborting. Observing whether a recovery unit is keeping a hole open is relatively simple. The harder part is instrumenting all of the possible blocking calls. The initial version should strive to at least cover:
|
| Comments |
| Comment by Githook User [ 12/May/20 ] |
|
Author: {'name': 'Jamie Heppenstall', 'email': 'jamie.heppenstall@mongodb.com', 'username': 'JamesHeppenstall'}Message: |