[SERVER-36267] Add replication metadata document to $backupCursor results Created: 25/Jul/18 Updated: 29/Oct/23 Resolved: 16/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| 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: | Storage NYC 2018-08-27 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If replication is enabled, the $backupCursor document source should additionally return a metadata document with three fields:
getLastStableCheckpointTimestamp should be used to acquire the checkpointTimestamp. Additionally, the design document dictates how to obtain the oplog start/end optimes. Note that during initial sync, the checkpointTimestamp may not exist. A backup in that state is of questionable value, but this project will not prohibit an application from taking one. |
| Comments |
| Comment by Githook User [ 16/Aug/18 ] |
|
Author: {'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb'}Message: |