-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2025-02-03, CAR Team 2025-02-17
-
200
SERVER-95650 has added checks ( 1, 2 ) inspecting the presence of the buckets collection to the commitTimeseriesBucket and commitTimeseriesBucketsAtomically methods in the timeries write path.
These checks were introduced alongside a lookup of the buckets collection from the collection catalog, followed by the propagation of the associated default collator to the introduced prepareCommit function.
However, this approach can lead to the buckets collection not being found when a concurrent operation transfers data of the given collection from shard A to shard B, and then drops that collection on the donor (after the insert has started but before the aforementioned code is reached). In this case a refresh due to a shard version mismatch would be expected instead.
- is related to
-
SERVER-100312 Re-enable timeseries_reshard_with_inserts.js
- In Progress
-
SERVER-100310 Temporarily disable timeseries_reshard_with_inserts.js
- Closed
- related to
-
SERVER-95650 Time-series inserts can use invalid string comparator
- Open
-
SERVER-92137 Make sure timeseries inserts perform a ShardVersion check before inspecting the existence of the buckets collection
- Closed