Hello community! When using AWS MSK as KafkaSourc...
# troubleshooting
c
Hello community! When using AWS MSK as KafkaSource, Has anyone experienced an issue where the offset of the consumer group is not committed even though checkpointing is completed After MSK's
security patch
?
d
Which Flink version? It could be related to this issue. fixed in Flink 1.16.0: https://issues.apache.org/jira/browse/FLINK-28060
c
I’m using flink 1.16.1..
d
Aha, probably not that then
c
I checked the dependencies of my flink application repo, I found that it was using confluent kafka-clients, which is compatible with version 2.8.x of Apache Kafka. If there are no problems with the next security patch, this is the cause.