[
https://issues.apache.org/jira/browse/NIFI-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14603551#comment-14603551
]
Brian Ghigiarelli commented on NIFI-732:
----------------------------------------
[~markap14] I'm testing out some changes to GetKafka that takes care of a lot
of these restart issues. Regarding the timeouts for Kafka and Zookeeper, it
looks like they're never used. Okay to take them out? Doesn't seem like much
use for us to timeout the processor, then restart it again on the next trigger
to wait some more. The Kafka Java Client handles the polling wait (current
functionality) pretty well. What do you think?
> GetKafka if stopped then started doesn't resume pulling messages
> ----------------------------------------------------------------
>
> Key: NIFI-732
> URL: https://issues.apache.org/jira/browse/NIFI-732
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Environment: linux
> Reporter: Joseph Witt
> Assignee: Mark Payne
> Fix For: 0.2.0
>
>
> A nifi user reported that they had to restart nifi to get the GetKafka
> processor to resume pulling data once they had stopped the processor. Upon
> restarting it showed that it was started but did not resume pulling data.
> Need to attempt to reproduce and resolve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
