Info

An example of this can be found in timeseries_serverStatus.js. Specifically, this scenario inserts two measurements, one that is far in the past and one that has the current time as its measurement. The measurements are inserted in [new, old] order. There is an existing bucket A that is eligible to take the current measurement but not the old one. In the old path, we would try to insert the new measurement first and then rollover the second bucket with timeBackward, causing it to be archived when we go to finish it's batch. In the new path, we sort the measurements, so the old measurement gets inserted first. It archives Bucket A, and allocates a new Bucket B to accept the insert. Then, when we go to insert the current measurement, Bucket B gets rolled over with time forward. Since time forward is a softClose rollover action, when we go to finish the batch for this bucket we also close it. This leads to the assertion that 'numBuckets' == 2 to fail in our new write path.

Top User Comments

JIRAUSER1269484 commented on Fri, 21 Mar 2025 21:15:35 +0000: The tests that are mentioned in this ticket, and that were failing in the patch build because they relied on the order of the inserts, have been patched in other tickets in this project/due to subsequent commits.

Steps to Reproduce