amazon-kinesis-producer icon indicating copy to clipboard operation
amazon-kinesis-producer copied to clipboard

processing_statistics_logger.cc throwing NaN value

Open infynyxx opened this issue 7 years ago • 7 comments

INFO  [2017-08-03 21:25:53,519] com.amazonaws.services.kinesis.producer.LogInputStreamReader: [2017-08-03 21:25:53.518979] [0x00000289][0x00007f35f1dc9700] [info] [processing_statistics_logger.cc:109] Stage 1 Triggers: { stream: '***', manual: 0, count: 0, size: 0, matches: 0, timed: 0, UserRecords: 0, KinesisRecords: 0 }
INFO  [2017-08-03 21:25:53,519] com.amazonaws.services.kinesis.producer.LogInputStreamReader: [2017-08-03 21:25:53.519060] [0x00000289][0x00007f35f1dc9700] [info] [processing_statistics_logger.cc:112] Stage 2 Triggers: { stream: '***', manual: 0, count: 0, size: 0, matches: 0, timed: 0, KinesisRecords: 0, PutRecords: 0 }
INFO  [2017-08-03 21:25:53,519] com.amazonaws.services.kinesis.producer.LogInputStreamReader: [2017-08-03 21:25:53.519077] [0x00000289][0x00007f35f1dc9700] [info] [processing_statistics_logger.cc:127] (segments) Average Processing Time: -nan ms

Version: 0.12.5

infynyxx avatar Aug 03 '17 21:08 infynyxx

Thank you for the feedback. We will prioritize it accordingly against the other customer requests.

sahilpalvia avatar Aug 21 '17 20:08 sahilpalvia

Hi @infynyxx @sahilpalvia , I ran into this too. What does it mean? Does it indicate that KPL is losing data, or just a small bug in logging? I'm not a c++ guy, and would appreciate your insights.

Thanks!

bowenli86 avatar Aug 25 '17 06:08 bowenli86

Yeah, seems like a small logging bug coming from https://github.com/awslabs/amazon-kinesis-producer/blob/v0.12.5/aws/utils/processing_statistics_logger.cc#L127

infynyxx avatar Aug 25 '17 14:08 infynyxx

This means the KPL isn't receiving any work, but it will still publish trigger information. If you're not currently pushing data to the stream the NAN values can safely be ignored. If you are sending data to the stream, this could indicate a problem.

pfifer avatar Aug 25 '17 15:08 pfifer

I ran into this issue too. Does it mean that the data sent to the stream is lost?

pooja84k avatar Sep 12 '18 18:09 pooja84k

I also get InvalidClientTokenId over time.

jef avatar Oct 07 '19 19:10 jef

We are getting similar issue. We are running KPL from onprem linux servers. We tested with KPL versions (0.13.1) and (0.12.11). Below are message we are seeing. Metric upload failing. This is happening while processing data. KPL successfully placing messages to Kinesis stream but cloudwatch not writing KPL Metrics.

[2020-06-04 14:55:06.579413] [0x00002aa4] [info] [processing_statistics_logger.cc:109] Stage 1 Triggers: { stream: 'stream-name-removed', manual: 0, count: 0, size: 0, matches: 0, timed: 0, UserRecords: 0, KinesisRecords: 0 } [2020-06-04 14:55:06.579413] [0x00002aa4] [info] [processing_statistics_logger.cc:112] Stage 2 Triggers: { stream: 'stream-name-removed', manual: 0, count: 0, size: 0, matches: 0, timed: 0, KinesisRecords: 0, PutRecords: 0 } [2020-06-04 14:55:06.579413] [0x00002aa4] [info] [processing_statistics_logger.cc:127] (stream-name-removed) Average Processing Time: -nan(ind) ms [2020-06-04 14:55:28.708604] [0x00001e50] [warning] [metrics_manager.cc:147] Metrics upload failed, but will retry. | Code: | Message: (Code: and Message: are actually empty not removed by me)

rajendrapallala avatar Jun 04 '20 19:06 rajendrapallala