[SERVER-53983] Block catalog cache refresh in resharding unit test in order to guarantee error received Created: 22/Jan/21 Updated: 29/Oct/23 Resolved: 16/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Sharding-NYC, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2021-02-22 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Story Points: | 1 | ||||
| Description |
|
Behavior was recently changed so that calling a catalog cache refresh with allowLocks: false no longer automatically throws an error. The aim of this ticket is to find another way to bring about the error for this test case, or alternatively find a solid way to argue that we don't need the test case any longer, since the behavior has changed. More context available in the linked BF, where tommaso.tocci found a place for a sleep that will constantly trigger the test case's failure. |
| Comments |
| Comment by Githook User [ 16/Feb/21 ] |
|
Author: {'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}Message: |