[SERVER-80200] Temporarily do not enforce constraints when fetching active transaction history Created: 17/Aug/23 Updated: 29/Oct/23 Resolved: 18/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution NAMR Team 2023-08-21, Execution NAMR Team 2023-09-04 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 135 | ||||||||||||
| Description |
|
Usually we'll only fetch active transaction history (via reading from config.transactions as a primary, but we have seen some cases where a service in the server can end up doing this briefly as a secondary when stepping down. This is fine conceptually since no writes will be able to occur once secondary, but it can cause this assertion to fail. Until we have a better solution for representing this state of being stepped down but not performing oplog application yet, we can just relax constraints for this read. |
| Comments |
| Comment by Githook User [ 18/Aug/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |