SpanToDT timestamp bug
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
#3 Updated by Derik Barseghian over 10 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:
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