[SERVER-61811] Do not run indexed_insert_where.js on concurrency_sharded_causal_consistency_and_balancer Created: 30/Nov/21 Updated: 29/Oct/23 Resolved: 21/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
indexed_insert_where.js performs finds with $where, which are not very performant. This can cause failures when running on the concurrency_sharded_causal_consistency_and_balancer suite: This suite does secondary reads. In case of find on a secondary that runs longer than orphanCleanupDelaySecs, the range deleter could kick in before the query on the secondary has finished and remove the documents the query expected to find. ( Since indexed_insert_where.js is know to run 'finds' that could take longer than the default orphanCleanupDelaySecs in our tests (1 second), we should not run this test on the concurrency_sharded_causal_consistency_and_balancer suite. |
| Comments |
| Comment by Githook User [ 21/Apr/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |