[SERVER-64049] Investigate read behavior of unsharded/sharded collections during yields Created: 28/Feb/22 Updated: 06/Dec/22 Resolved: 02/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Cox (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
The owner of this ticket should investigate if the critical section is checked during a yield. It seems that there are no such checks baked into the query plan. Suppose a collection begins unsharded, a query runs then yields and then becomes sharded. On yield recovery what is the behavior of the system in this scenario? |