Project

General

Profile

Bug #5253

SpanToDT timestamp bug

Added by Derik Barseghian over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
sensor-view
Target version:
Start date:
12/08/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5253

Description

SpanToDT has a bug that Dan and I tracked down today. DataTurbine outputs errors like:

Cannot add frame to gpp, it starts before the end of the previous frame.
End of previous frame: 1.291854708E9 Start of new frame: 1.291854679E9

This is because a line in PeriodicReadFullMetadataThread uses the system that's running SpanToDT's clock:
SpanMetadata.SensorMetadata metadata = new SpanMetadata.SensorMetadata(fullName, new Date(), sensorMetadata);

derik_: why's that line using a new Date()? shouldn't it just use the corresponding sensor date?
crawl: SpanToDT periodically queries all the metadata for each sensor, the frequency set by that arg
crawl: in this case it comes from the control port, not the live metadata port
crawl: the fix is to use the timestamp in the response

History

#1 Updated by Derik Barseghian over 8 years ago

changing bugs from REAP to Kepler product

#2 Updated by Daniel Crawl over 8 years ago

This was fixed in r26493.

#3 Updated by Derik Barseghian over 8 years ago

I still get this error sometimes, e.g.

459 <01-Apr-2011 Pacific Daylight Time 13:21:44.088> <gpp>
460 Reconnected with the following channels:
461 CR800_Batt_Volt
462 CR800_Batt_Volt_metadata
463 CR800_sq311_1
464 CR800_sq311_1_metadata
465 CR800_sq311_2
466 CR800_sq311_2_metadata
467 <01-Apr-2011 Pacific Daylight Time 13:22:42.118> <gpp>
468 Cannot add frame to gpp, it starts before the end of the previous frame.
469 End of previous frame: 1.30171450367E9 Start of new frame: 1.301714502709E9

#4 Updated by Daniel Crawl over 8 years ago

This appears to be fixed by inserting data and metadata as separate sources.

#5 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5253

Also available in: Atom PDF