Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-8542

Do not indefinitely store closed shard's state in the FlinkKinesisConsumer

    XMLWordPrintableJSON

Details

    Description

      See original discussion here: https://github.com/apache/flink/pull/5337

      Currently, the Kinesis consumer keeps a list of (StreamShardMetadata, SequenceNumber) as its state. That list also contains all shards that have been closed already, and is kept in the state indefinitely so that on restore, we know that a closed shard is already fully consumed,

      The downside of this, is that the state size of the Kinesis consumer can basically grow without bounds, as the consumed Kinesis streams are resharded and more and more closed shards are present.

      Some possible solutions have been discussed in the linked PR comments.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tzulitai Tzu-Li (Gordon) Tai
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: