[SERVER-83119] Secondary replica crashes on clustered collection if notablescan is enabled Created: 10/Nov/23 Updated: 02/Feb/24 Resolved: 12/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.3.0, 5.0.0, 6.0.0, 7.0.0, 7.2.0-rc0 |
| Fix Version/s: | 7.2.1, 7.3.0-rc0, 7.0.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Peter Volk |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v7.2, v7.0, v6.0, v5.0
|
||||||||||||||||||||||||
| Sprint: | QO 2023-12-11, QO 2023-12-25, QO 2024-01-08, QO 2024-01-22 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 145 | ||||||||||||||||||||||||
| Description |
|
On a clustered collection when notablescan is enabled:
In this scenario, the plan for the delete by _id on the secondary would include a CLUSTERED_IXSCAN and thus should not be blocked by the notablescan setting. The solution is to fix the planner logic to allow CLUSTERED_IXSCAN with the notablescan setting. See the repro script in the comment below and see the code here |
| Comments |
| Comment by Githook User [ 02/Feb/24 ] |
|
Author: {'name': 'Peter Volk', 'email': '77723508+HCSPete@users.noreply.github.com', 'username': 'HCSPete'}Message: GitOrigin-RevId: 19aee73de8ff18e3b18ff98fca5458e44fe2d09f |
| Comment by Githook User [ 18/Jan/24 ] |
|
Author: {'name': 'Peter Volk', 'email': 'peter.volk@mongodb.com', 'username': 'HCSPete'}Message: |
| Comment by Githook User [ 11/Jan/24 ] |
|
Author: {'name': 'Peter Volk', 'email': '77723508+HCSPete@users.noreply.github.com', 'username': 'HCSPete'}Message: GitOrigin-RevId: 0556bfee1e398617dca5703e8eb75487bef23f3e |
| Comment by Chris Hutchinson [ 17/Nov/23 ] |
|
bernard.gorman@mongodb.com steve.tarzia@mongodb.com Reassigning this bug to QO - sounds like we need to relax the query planner so that it will produce a bounded clustered collection scan even when. notablescan is enabled. cc david.storch@mongodb.com |