[jira] [Commented] (NIFI-732) GetKafka if stopped then started doesn't resume pulling messages

["Mark Payne (JIRA)" <ji...@apache.org>]

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

Mark Payne commented on NIFI-732:
---------------------------------

[~brianghig] I'd be hesitant to remove the timeouts. We should probably make proper use of them. The issue with removing them is that if it never gets a response, and the user clicks Stop, the processor will never stop. It will just sit and wait indefinitely to finish reading from the socket.

> 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)