-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
v8.2, v8.0, v7.0
-
CAR Team 2025-11-10
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently, executing a write operation triggering a catalog refresh during a primary re-election may result in an InterruptedDueToReplStateChange error. This error is thrown when the re-election occurs immediately after registering the term, hitting this uassert. Given that InterruptedDueToReplStateChange is a transient error, we should add the InterruptedDueToReplStateChange error, or more generally the retriable error category (which Iincludes InterruptedDueToReplStateChange), to the acceptable errors in the catalog cache retry loop. In this way, the refresh can be retried and succeed once the primary re-election has completed.