[SERVER-40751] BatchWriteOp::noteBatchError doesn't update it's state to error if there are child ops still in pending Created: 19/Apr/19 Updated: 29/Oct/23 Resolved: 01/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| 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: | Sharding 2019-04-22, Sharding 2019-05-06 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
This is because of the condition here. For normal writes, the executor would try to move them into a state where all child ops would have a state that's not pending, but because we stop early for transactions, it is possible to end up in this situation. |
| Comments |
| Comment by Githook User [ 01/May/19 ] |
|
Author: {'email': 'randolph@10gen.com', 'name': 'Randolph Tan', 'username': 'renctan'}Message: |