You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Elias Levy (JIRA)" <ji...@apache.org> on 2019/01/28 17:14:00 UTC
[jira] [Commented] (FLINK-11435) Different jobs same consumer group
are treated as separate groups
[ https://issues.apache.org/jira/browse/FLINK-11435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754156#comment-16754156 ]
Elias Levy commented on FLINK-11435:
------------------------------------
This is expected behavior. Flink manages Kafka offsets itself. Offsets are only reported to Kafka via the consumer group id to allow tracking progress by tools in Kafka ecosystem.
> Different jobs same consumer group are treated as separate groups
> -----------------------------------------------------------------
>
> Key: FLINK-11435
> URL: https://issues.apache.org/jira/browse/FLINK-11435
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector
> Affects Versions: 1.7.1
> Environment: kafka consumer
> Reporter: Avi Levi
> Priority: Major
>
> deploying two jobs with the same consumer group id, still treated as different consumer groups. This behavior does not comply with kafka expectations. Same consumer group ids should be treated as the same group this will enable deploying more jobs (specially if they are stateless ) on demand and it also how normal consumer groups behave.
> reproduce :
> deploy the same job twice - both jobs consumes the same message although they share the same consumer id
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)