-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2024-11-11, CAR Team 2024-11-25, CAR Team 2024-12-09
-
2
When a StaleDbVersion, StaleConfig, or ShardCannotRefreshDueToLocksHeld exception is triggered in the Service Entry Point, a refresh is performed and the command is retried (code).
The decision to retry the command depends on certain conditions. For example, we cannot retry the command when executing a getMore, as the cursor may already be lost.
This retry policy only applies when the error from the original command is StaleConfig or ShardCannotRefreshDueToLocksHeld, and not StaleDbVersion.
The goal of this ticket is to investigate if we can have a consistent retry approach for all three stale config exceptions for the getMore command.