Resharding a timeseries during insertion does not leave the bucket collection optimally compressed

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Kshitij Gupta (Inactive)
              Reporter:
              Enrico Golfieri
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: