[SERVER-70183] sbe_plan_cache_autoparameterize_collscan.js should not run in shard_merge_jscore_passthrough suite Created: 03/Oct/22 Updated: 29/Oct/23 Resolved: 05/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| 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: | QE 2022-10-17 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 45 | ||||||||||||
| Description |
|
This test explicitly checks the contents of the SBE plan cache. The plan cache is local to a given node and will never replicate or migrate as part of tenant migrations. shard_merge_jscore_passthrough does tenant migrations in the background, and therefore the client can switch from operating against one replica set to another in the middle of the test. This can cause the perceived state of the plan cache to change out from under the test's feet since the physical mongod node backing the test has changed. Therefore, any test which explicitly interrogates plan cache state must be excluded from shard_merge_jscore_passthrough. |
| Comments |
| Comment by Githook User [ 05/Oct/22 ] |
|
Author: {'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}Message: |