[
https://issues.apache.org/jira/browse/STORM-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282584#comment-16282584
]
Stig Rohde Døssing edited comment on STORM-2847 at 12/7/17 9:51 PM:
--------------------------------------------------------------------
[~erosebrook] Those line numbers don't match up with the line numbers from
1.x-branch (the 1.2.0 branch). See for example
https://github.com/apache/storm/blob/1.x-branch/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java#L328
which is supposed to be where emitTupleIfNotEmitted starts according to the
stack trace. We haven't merged anything to storm-kafka-client since a few days
ago as far as I know. I checked 1.1.x-branch, 1.0.x-branch and master as well
(1.0.6, 1.1.2 and 2.0.0 respectively) and the line numbers don't match up to
your stack trace either.
I'm assuming the new stack trace is unrelated to the original, since the new
trace doesn't contain
org.apache.storm.kafka.spout.KafkaSpout.commitOffsetsForAckedTuples(KafkaSpout.java:473)?
It would be good if you could find the commit hash you built from.
was (Author: srdo):
[~erosebrook] Those line numbers don't add up with the line numbers from
1.x-branch (the 1.2.0 branch). See for example
https://github.com/apache/storm/blob/1.x-branch/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java#L328
which is supposed to be where emitTupleIfNotEmitted starts according to the
stack trace. We haven't merged anything to storm-kafka-client since a few days
ago as far as I know. I checked 1.1.x-branch, 1.0.x-branch and master as well
(1.0.6, 1.1.2 and 2.0.0 respectively) and the line numbers don't match up to
your stack trace either.
I'm assuming the new stack trace is unrelated to the original, since the new
trace doesn't contain
org.apache.storm.kafka.spout.KafkaSpout.commitOffsetsForAckedTuples(KafkaSpout.java:473)?
It would be good if you could find the commit hash you built from.
> 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)
