ui: new nodes retroactively get non-zero range count on timeseries (v2.0.0)

[nstewart]

I have a cluster 3 node cluster that I scaled up to 6 nodes. Everything re-balanced but when I look at range counts early in the time series I see nodes 4,5, and 6 have a small number of ranges even though they were not yet created at that time.

This problem only shows up if I'm at a time range when all 6 nodes appear at some point.

The 99% latency chart correctly shows the additional nodes at 0 before they actually come online.

[couchand]

I'm pretty sure this is the same phenomenon as #23480.