Resolved a trace where a timestamp had an faulty offset of -1 in the aggregation deamon
This commit is contained in:
parent
5f5597dae4
commit
e4532031e3
1 changed files with 1 additions and 1 deletions
|
|
@ -110,7 +110,7 @@ public class SensorDataAggregatorDaemon implements HalDaemon {
|
||||||
long latestCompletePeriodEndTimestamp = new UTCTimePeriod(aggregationStartTime, aggrPeriodLength).getPreviosPeriod().getEndTimestamp();
|
long latestCompletePeriodEndTimestamp = new UTCTimePeriod(aggregationStartTime, aggrPeriodLength).getPreviosPeriod().getEndTimestamp();
|
||||||
long oldestPeriodStartTimestamp = new UTCTimePeriod(aggregationStartTime-ageLimitInMs, aggrPeriodLength).getStartTimestamp();
|
long oldestPeriodStartTimestamp = new UTCTimePeriod(aggregationStartTime-ageLimitInMs, aggrPeriodLength).getStartTimestamp();
|
||||||
|
|
||||||
if(latestCompletePeriodEndTimestamp == oldestPeriodStartTimestamp){
|
if(latestCompletePeriodEndTimestamp == maxTimestampFoundForSensor){
|
||||||
logger.fine("no new data to evaluate - aggregation is up to date");
|
logger.fine("no new data to evaluate - aggregation is up to date");
|
||||||
}else{
|
}else{
|
||||||
logger.fine("evaluating period: "+ (maxTimestampFoundForSensor+1) + "=>" + latestCompletePeriodEndTimestamp + " (" + UTCTimeUtility.getDateString(maxTimestampFoundForSensor+1) + "=>" + UTCTimeUtility.getDateString(latestCompletePeriodEndTimestamp) + ") with expected sample count: " + expectedSampleCount);
|
logger.fine("evaluating period: "+ (maxTimestampFoundForSensor+1) + "=>" + latestCompletePeriodEndTimestamp + " (" + UTCTimeUtility.getDateString(maxTimestampFoundForSensor+1) + "=>" + UTCTimeUtility.getDateString(latestCompletePeriodEndTimestamp) + ") with expected sample count: " + expectedSampleCount);
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue