[SERVER-67794] Use shard split document abortReason if it already exists Created: 05/Jul/22 Updated: 29/Oct/23 Resolved: 12/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Didier Nadeau | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-07-25 |
| Participants: |
| Description |
|
If a shard split operation is started using an kAborted document with an abortReason, we do not currently use the abortReason and return it to the caller. This means the return value of `commit()` can change if it's re-run on another primary (i.e. if there's a stepdown during the operation). We need to address this. |
| Comments |
| Comment by Githook User [ 12/Jul/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |