[SERVER-76237] Default YieldPolicy for UpdateRequest and DeleteRequest should be YIELD_AUTO Created: 18/Apr/23 Updated: 30/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
The default policy for UpdateRequest and DeleteRequest is NO_YIELD, which is dangerous (see
|
| Comments |
| Comment by David Storch [ 21/Apr/23 ] |
|
Now that I'm caught up on this: I'd say that this would be a good candidate for a quick win. I don't think we are aware of this causing a bug today, but the proposed improvement would make a future bug where we fail to set the yield policy correctly less likely. |
| Comment by Kyle Suarez [ 18/Apr/23 ] |
|
Leaving this in the triage queue – david.storch@mongodb.com is reviewing some of louis.williams@mongodb.com's other work and he will report back here with more info. |