You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If data is present/ingested that should be aged off, you can get a SOE during compaction or at scan time due to the recursive call chain in the MetricAgeOffIterator:
seekPastAgedOffMetricData(line 161)
seekIfNecessary(line 87)
seek(line 180)
The text was updated successfully, but these errors were encountered:
This occurred due to an error on the client where it was sending data at second precision instead of millisecond precision thus creating very old data. I wonder if the solution here is to drop data if it's date/time is before the configured age-off setting for the metric.
Maybe in this case, an interval drop rule would be more successful via it discretizes the time interval of the segment at a specific granularity to generate a table of set time points.
If data is present/ingested that should be aged off, you can get a SOE during compaction or at scan time due to the recursive call chain in the MetricAgeOffIterator:
seekPastAgedOffMetricData(line 161)
seekIfNecessary(line 87)
seek(line 180)
The text was updated successfully, but these errors were encountered: