[SERVER-68938] Examine if retry loop is needed in cases with RSLocalClient().queryOnce() Created: 18/Aug/22 Updated: 27/Oct/23 Resolved: 09/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
In catalog shard POC, some generic Shard based queries with retry are replaced with RSLocalClient().queryOnce() without retry. Using ShardingCatalogClientHelper that can be used for retry loops is problematic in some cases because it has high level dependencies and creates a dependency loop, preventing the build. Most likely, we don't need to do anything, but this requires discussion. |
| Comments |
| Comment by Jack Mulrow [ 09/Feb/23 ] |
|
Temporary issue from the POC which has since been finished. |