[SERVER-62925] Rationalize locking behavior for sbe exchange operator Created: 24/Jan/22 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Svilen Mihaylov (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sbe | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
Currently we take a global lock when on operator open. Is this the right approach? Lock::GlobalLock lock(opCtx, MODE_IS);
Without this locking we can fail parallel plans with indexes by asserting here boost::optional<KeyStringEntry> seekForKeyString( |