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

ASF GitHub Bot commented on NIFI-2322:
--------------------------------------

GitHub user olegz opened a pull request:

    https://github.com/apache/nifi/pull/741

    NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements

    - Fixed KafkaConsumer's connection block when broker is not available
    - Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
    - Added sensitive properties for SSL ket/trust stores

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/olegz/nifi NIFI-2322

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/741.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #741
    
----
commit bd9172473293c6be4d0287b62f8c91a4b068bd8b
Author: Oleg Zhurakousky <[email protected]>
Date:   2016-07-29T13:06:47Z

    NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
    - Fixed KafkaConsumer's connection block when broker is not available
    - Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
    - Added sensitive properties for SSL ket/trust stores

----


> ConsumeKafka gets stuck (cannot be stopped)
> -------------------------------------------
>
>                 Key: NIFI-2322
>                 URL: https://issues.apache.org/jira/browse/NIFI-2322
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.0.0
>            Reporter: Haimo Liu
>            Assignee: Oleg Zhurakousky
>             Fix For: 1.0.0
>
>         Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to