[SERVER-85548] Time series insert may return collection not found error Created: 22/Jan/24 Updated: 23/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | time-series | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 155 | ||||||||||||||||
| Description |
|
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. |