-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
After SERVER-83878 , unsharded timeseries can be tracked on the sharding catalog and consequently moved by the balancer using moveCollection (and therefore resharding).
However jstests/core/timeseries/timeseries_simple.js started failing consistently when running with balancer active ( sharding_jscore_passthrough_with_balancer) as in case a resharding operation happens during the insertions, the bucket collection will end up with more then 1 collection.
There is no data loss, simply the compression seems not to be optimal as the test expected only 1 collection.
The check has been temporarily disabled in case of balancer enabled until this ticket is fixed.
- depends on
-
SERVER-83878 Support tracking unsharded timeseries collections in the sharding catalog
- Closed
- is related to
-
SERVER-89584 Timeseries writes should handle ShardCannotRefreshDueToLocksHeld error correctly.
- Closed
- related to
-
SERVER-89629 Complete TODO listed in SERVER-89349
- Closed