You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Seweryn Habdank-Wojewodzki (JIRA)" <ji...@apache.org> on 2017/10/10 14:52:00 UTC
[jira] [Commented] (KAFKA-4905) StreamPartitionAssignor doesn't
respect subscriptions to assign partitions.
[ https://issues.apache.org/jira/browse/KAFKA-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198776#comment-16198776 ]
Seweryn Habdank-Wojewodzki commented on KAFKA-4905:
---------------------------------------------------
[~fredriv] What exactly means: "Just needed to scale down old cluster completely"? How to do this in production without stopping other services based on Kafka? Thanks in advance.
> StreamPartitionAssignor doesn't respect subscriptions to assign partitions.
> ---------------------------------------------------------------------------
>
> Key: KAFKA-4905
> URL: https://issues.apache.org/jira/browse/KAFKA-4905
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.2.0
> Reporter: Florian Hussonnois
>
> Both RangeAssignor and RoundRobinAssignor use the subscriptions to assign partition to each consumer. This allow to have two consumers belonging to the the same group and subscribing to two differents topics.
> This doesn't seem to be the case of the StreamPartitionAssignor resulting to an IllegalArgumentException thrown during rebalance.
> java.lang.IllegalArgumentException: Assigned partition foo-2 for non-subscribed topic regex pattern; subscription pattern is bar
> at org.apache.kafka.clients.consumer.internals.SubscriptionState.assignFromSubscribed(SubscriptionState.java:190)
> at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinComplete(ConsumerCoordinator.java:216)
> at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:352)
> at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:303)
> This is because the consumer group leader attempt to assign partitions to a consumer that didn't subscribe to the associated topic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)