[
https://issues.apache.org/jira/browse/STORM-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084393#comment-16084393
]
Kristopher Kane commented on STORM-2554:
----------------------------------------
I mentioned it in the PR but adding it here in case it was missed:
I had a parallel effort which arrived at most of the same conclusions before
discovering this JIRA.
There is a bug with activate/deactivate where the spout continues to call
nextTuple() but never emits new messages. I'm not sure if it is scoped to the
manual partition work or is a general bug. Would you consider a fix here for
that or a new JIRA?
#############
Since posting that, I have a fix for nulling out the currentAssignment and it
enables the ability to deactivate and activate, however, I'm seeing duplicates
during reactivate. I'm also seeing duplicates if you kill the topology and
start it back up at 'uncommitted_earliest'
> Trident Kafka Spout Refactoring to Include Manual Partition Assignment
> ----------------------------------------------------------------------
>
> Key: STORM-2554
> URL: https://issues.apache.org/jira/browse/STORM-2554
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
> Affects Versions: 2.0.0, 1.x
> Reporter: Hugo Louro
> Assignee: Hugo Louro
> Priority: Critical
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Incorporate changes done in STORM-2541 and do some refactoring to internal
> state partition management to make it cleaner and more properly handle
> partitions reassignment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
