-
Notifications
You must be signed in to change notification settings - Fork 107
Panic when merging series #1095
Comments
@DanCech do you know this can be reproduced ? |
likely same as #761 |
Looking at the customer's query, I see that we have series with the same name and different intervals (10 and 60), which get merged While I didn't have a tool handily available to exercise what happens with series changing intervals, I am able to get close by sending different series and just measuring their length like so:
then, launching
confirm the series:
this works fine but shows that it would break if they were to be merged:
likewise, can trigger a similar problem in
|
i'll dig deeper, but it looks like series with interval=10 have points like:
those with interval 600 have
checked this in getTargets, and also i saw they have the same values for: |
All series should have the same number of points as the interval of all series should be the same due to https://github.com/grafana/metrictank/blob/master/api/query_engine.go#L30 |
See my comment here In #913 Here is my local hack-around Edit: I don't think this is correct solution as it kind of "fudges" the timestamps to match up, but it more or less works. |
Seems to be the same as #874 |
The code on https://github.com/grafana/metrictank/blob/master/api/dataprocessor.go#L624 assumes when merging series that they all have the same number of data points. If that is not true, then it can panic for "runtime error: index out of range"
The text was updated successfully, but these errors were encountered: