Re: Encountered the following Expired Iterator exception in getRecords using FlinkKinesisConsumer

2018-12-14 Thread Vijay Balakrishnan
I have 2 shards in the Kinesis Streams- need to figure out how to check from the logs if records are being written to both shards . Not sure if this is what you are looking for in terms of # of shards read- seems like 1 from the logs below: DEBUG org.apache.http.wire

Re: Encountered the following Expired Iterator exception in getRecords using FlinkKinesisConsumer

2018-12-14 Thread Tzu-Li (Gordon) Tai
Hi, I’m suspecting that this is the issue:  https://issues.apache.org/jira/browse/FLINK-11164. One more thing to clarify to be sure of this: Do you have multiple shards in the Kinesis stream, and if yes, are some of them actually empty? Meaning that, even though you mentioned some records were

Re: Encountered the following Expired Iterator exception in getRecords using FlinkKinesisConsumer

2018-12-13 Thread Vijay Balakrishnan
Hi Gordon, My use-case was slightly different. 1. Started a Kinesis connector source, with TRIM_HORIZON as the startup position. 2. Only a few Records were written to the Kinesis stream 3. The FlinkKinesisConsumer reads the records from Kinesis stream. Then after a period of time of not reading

Re: Encountered the following Expired Iterator exception in getRecords using FlinkKinesisConsumer

2018-12-13 Thread Tzu-Li (Gordon) Tai
Hi! Thanks for reporting this. This looks like an overlooked corner case that the Kinesis connector doesn’t handle properly. First, let me clarify the case and how it can be reproduced. Please let me know if the following is correct: 1. You started a Kinesis connector source, with