[SERVER-41987] Update comment in repl/oplog.cpp on timestamping rules Created: 27/Jun/19 Updated: 29/Oct/23 Resolved: 12/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18 |
| Participants: |
| Description |
|
This block in applyOperations_inlock outlines the timestamping rules and their uses cases. This comment is out of date and does not give us the full picture. For example, we replay prepared transactions in a timestamped WUOW, which does not fall under any of the categories there. |
| Comments |
| Comment by Githook User [ 12/Nov/19 ] |
|
Author: {'name': 'Tess Avitabile', 'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com'}Message: |