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

ASF GitHub Bot commented on KAFKA-5434:
---------------------------------------

GitHub user ppatierno opened a pull request:

    https://github.com/apache/kafka/pull/3335

    KAFKA-5434: Console consumer hangs if not existing partition is specified

    Added checking partition exists before assign request

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

    $ git pull https://github.com/ppatierno/kafka kafka-5434

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

    https://github.com/apache/kafka/pull/3335.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 #3335
    
----
commit 44bbb65994a957866ffc9b7574a4e40870c4f69f
Author: ppatierno <ppatie...@live.com>
Date:   2017-06-14T08:22:53Z

    Added checking partition exists before assign request

----


> Console consumer hangs if not existing partition is specified
> -------------------------------------------------------------
>
>                 Key: KAFKA-5434
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5434
>             Project: Kafka
>          Issue Type: Bug
>          Components: tools
>            Reporter: Paolo Patierno
>            Assignee: Vahid Hashemian
>
> Hi,
> if I specify the --partition option for the console consumer with a not 
> existing partition for a topic, the application hangs indefinitely.
> Debugging the code I see that it asks for metadata but when it receives topic 
> information and it doesn't find the requested partition inside such metadata, 
> the code retries new time.
> Could be it worst to check if the partition exists using the partitionFor 
> method before calling the assign in the seek of the BaseConsumer and throwing 
> an exception so printing an error on the console ?
> Thanks,
> Paolo



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

Reply via email to