[SERVER-53513] Update config.transactions for committed transactions before startFetchingOpTime Created: 23/Dec/20 Updated: 29/Oct/23 Resolved: 03/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-H | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2021-03-08 | ||||||||
| Participants: | |||||||||
| Description |
|
We will need to write a new type of noop oplog entry that secondaries can observe to also update their config.transactions. |
| Comments |
| Comment by Githook User [ 03/Mar/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |
| Comment by Githook User [ 01/Mar/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |
| Comment by Esha Maharishi (Inactive) [ 04/Jan/21 ] |
|
Summarizing Slack conversation - the recipient should include a filter for config.transactions entries having a lastWriteOpTime.ts less than the startFetchingTimestamp. See example here. |