-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
ALL
-
155
If the catalog state changes in certain ways during an insert command to a time series collection (e.g. collection is dropped, or we enter replication rollback), we may report an error to the user that the collection was not found. This is somewhat confusing behavior, as for normal collections we would implicitly create the collection. We should be able to handle this more transparently by adding some higher-level retry logic to restart the command when such a catalog change is detected.
- duplicates
-
SERVER-57793 Inserting into a time-series collection can fail with NamespaceNotFound
-
- Closed
-
- is related to
-
SERVER-92137 Timeseries inserts may fail with NamespaceNotFound after moveCollection
-
- Closed
-
- related to
-
SERVER-85557 Return more helpful error when time series insert fails due to catalog state change
-
- Closed
-