Re: Deadlock in Subtask in the FlinkKinesisConsumer

Hi Seth, I think the global watermark / mark as idle is one of the reasons why the FLIP-27 [1] interfaces were created, while FLIP-180 [2] is also relevant here. Unfortunately, the FlinkKinesisConsumer is still using the old interface. I'm not sure it can be properly fixed with the old interfaces.

Deadlock in Subtask in the FlinkKinesisConsumer

Hi I wanted to bring awareness to this Jira describing a deadlock state we've experienced for a single subtask in the FlinkKinesisConsumer. This occurs when we've reached the following conditions in the subtask: - reached the max lookahead so th