[ 
https://issues.apache.org/jira/browse/STORM-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297678#comment-16297678
 ] 

Erik Weathers commented on STORM-2844:
--------------------------------------

[~hmclouro]: this ticket indicates the affected versions as 1.2.0 and 2.0.0, 
but the ticket that introduced the problem (STORM-2666) indicates that it is 
targeted for 1.1.2 as well (1.1.2 is in the Fix Versions field, and I see the 
commit in the 1.1.x-branch).  So I think this ticket (STORM-2844) be backported 
to the 1.1.x-branch as well.

> KafkaSpout Throws IllegalStateException After Committing to Kafka When First 
> Poll Strategy Set to EARLIEST
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-2844
>                 URL: https://issues.apache.org/jira/browse/STORM-2844
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka-client
>    Affects Versions: 2.0.0, 1.2.0
>            Reporter: Hugo Louro
>            Assignee: Hugo Louro
>            Priority: Critical
>              Labels: pull-request-available
>          Time Spent: 10h 50m
>  Remaining Estimate: 0h
>
> This 
> [code|https://github.com/apache/storm/blob/1.x-branch/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/KafkaSpout.java#L407-L409],
>  which was committed to fix 
> [STORM-2666|https://issues.apache.org/jira/browse/STORM-2666] throws 
> IllegalStateException when the KafkaSpout commits to Kafka and is restarted 
> with the same consumer group id and first poll strategy is set to EARLIEST.
> For example consider the following sequence:
> # KafkaSpout with consumer_group_id=TEST polls and commits offsets 1-5 
> # KafkaSpout with consumer_group_id=TEST is restarted with first poll 
> strategy set to EARLIEST
> ==> IllegalStateException will be thrown
> This bug could be a blocker. I am setting it to Critical because assigning a 
> different consumer id serves as a workaround to the problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to