[SERVER-39782] Replaying prepared transaction writes for commit oplog entry during replication recovery and initial sync should set commit and durable timestamp for those writes. Created: 22/Feb/19 Updated: 29/Oct/23 Resolved: 28/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| 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: | Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Currently, when we commit a prepared transaction as a part of commit oplog replay, we don't set any timestamp (commit & durable timestamp) to the wiredTiger transaction via recovery unit. So, basically we are committing the write operations as non-timestamped. This would cause problem for data visibility and durability. |
| Comments |
| Comment by Githook User [ 28/Mar/19 ] |
|
Author: {'email': 'suganthi.mani@mongodb.com', 'name': 'Suganthi Mani', 'username': 'smani87'}Message: |