[
https://issues.apache.org/jira/browse/STORM-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284263#comment-16284263
]
Stig Rohde Døssing edited comment on STORM-2847 at 12/8/17 9:41 PM:
--------------------------------------------------------------------
When you refer to triggering a rebalance what do you mean? Asking Storm to
rebalance the topology or something else?
Also as of 1.2.0 Kafka isn't responsible for managing consumer group partition
assignment anymore, the spout handles distributing partitions without
consulting Kafka. See https://issues.apache.org/jira/browse/STORM-2542 for why
we made this change. Partition assignment is now handled by
https://github.com/apache/storm/blob/master/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/subscription/ManualPartitionSubscription.java
and associated classes.
was (Author: srdo):
When you refer to triggering a rebalance what do you mean? Asking Storm to
rebalance the topology or something else?
> Exception thrown after rebalance IllegalArgumentException
> ---------------------------------------------------------
>
> Key: STORM-2847
> URL: https://issues.apache.org/jira/browse/STORM-2847
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
> Affects Versions: 1.2.0
> Reporter: Evan Rosebrook
> Assignee: Stig Rohde Døssing
>
> After rebalance the storm-kafka-client spout attempts to check the current
> position of partitions that are no longer assigned to the current spout. This
> occurs in a topology with multiple spout instances.
> java.lang.IllegalArgumentException: You can only check the position for
> partitions assigned to this consumer. at
> org.apache.kafka.clients.consumer.KafkaConsumer.position(KafkaConsumer.java:1262)
> at
> org.apache.storm.kafka.spout.KafkaSpout.commitOffsetsForAckedTuples(KafkaSpout.java:473)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)