I retrieve the first shard in node Red using "GetShardInterator" and "LATEST". After that I use this in "GetRecords" in a loop with 1 second delay.
I currently have all the sequence numbers written to a file coming out the output. At the error output below I have a debug, but so far it never generates any output.
In AWS, I have a Lambda function attached to the same Kinesis stream (shards there are sized large enough) using a trigger. This writes all sequence numbers to a log for me.
Within a very short time I can see that there are sequences in the log at AWS that never arrive at the output in NodeRed.
So it seems that they are never picked up.
I would like to investigate the problem further and also fix it. Unfortunately, I lack the further knowledge to do so.
What can I do next and where can I start?
Or maybe the problem is already known?
cwqh
commented
3 years ago
I retrieve the first shard in node Red using "GetShardInterator" and "LATEST". After that I use this in "GetRecords" in a loop with 1 second delay.
I currently have all the sequence numbers written to a file coming out the output. At the error output below I have a debug, but so far it never generates any output.
In AWS, I have a Lambda function attached to the same Kinesis stream (shards there are sized large enough) using a trigger. This writes all sequence numbers to a log for me. Within a very short time I can see that there are sequences in the log at AWS that never arrive at the output in NodeRed. So it seems that they are never picked up.
I would like to investigate the problem further and also fix it. Unfortunately, I lack the further knowledge to do so.
What can I do next and where can I start? Or maybe the problem is already known?