[SERVER-47410] ShardServerCatalogCacheLoader shouldn't replace error codes with OperationFailed Created: 08/Apr/20 Updated: 29/Oct/23 Resolved: 14/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc2, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Sharding 2020-04-20 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 12 | ||||||||
| Description |
|
The ShardServerCatalogCache loader currently replaces the error code of not ok statuses returned from several reads performed as part of a metadata refresh with OperationFailed - here, here, and here. This can prevent our test infrastructure from automatically retrying if the original error codes were retryable. Instead, the loader should preserve the original error codes, possibly by using uassertStatusOKWithContext() (e.g. here). |
| Comments |
| Comment by Githook User [ 20/Apr/20 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit be3eeca3c9802293b4a18cfae2d28c6cd41dfa29) |
| Comment by Githook User [ 14/Apr/20 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |