New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avg_over_time for multiple time series fails at durations over 3 hours #5556
Comments
Thanks for reporting @dandv ! Looks like this problem is caused by rollup cache enhancement for instant queries intorduced in 1.95. As a workaround, disable cache for queries by passing @zekker6 may I ask you to take a look at this issue? It seems to be like relevant to another issue you was involved is about preserving metric names for left and right parts of binary operators. |
This looks like a duplicate for #5659 and #5730 . These issues were addressed in v1.97.0 release. @dandv , could you verify whether the issue is fixed in |
…modifier is applied to binary operator Updates #5556
…modifier is applied to binary operator Updates #5556
@dandv , could you build VictoriaMetrics from the commit ec0ca8e according to these docs and verify whether it fixes the issue? |
The bugfix for this issue has been included in v1.97.1 release. Closing the issue as fixed then. @dandv , please re-open this issue if it still persists in |
Describe the bug
avg_over_time seems to call internally sum_over_time, then divide that by count_over_time. This works, but apparently not if the duration is longer than 2 hours, even though the series selected have one data point each, inserted within the last minute.
To Reproduce
If the duration is 3+ hours, the following error is returned:
Version
victoria-metrics-20231212-224437-tags-v1.96.0-0-g304fe0565
Logs
No warnings or errors.
Used command-line flags
-search.latencyOffset=1s
but the bug is reproduced without it as well.The text was updated successfully, but these errors were encountered: