[SERVER-72025] return blockTimestamp in the commitShardSplit response Created: 09/Dec/22 Updated: 29/Oct/23 Resolved: 19/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Matt Broadstone |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-12-26 |
| Participants: |
| Description |
|
If the commitShardSplit command returns { ok: 1 }, also include the blockTimestamp in that response. This is for point-in-time restores to use for stitching oplogs together. |
| Comments |
| Comment by Githook User [ 19/Dec/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |
| Comment by Esha Maharishi (Inactive) [ 12/Dec/22 ] |
|
matt.broadstone@mongodb.com would you be able to pick this up this sprint? |