storm-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STORM-380) Kafka spout: throw RuntimeException if a leader cannot be found for a partition
Date Thu, 10 Jul 2014 03:15:05 GMT

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

ASF GitHub Bot commented on STORM-380:
--------------------------------------

Github user ptgoetz commented on the pull request:

    https://github.com/apache/incubator-storm/pull/170#issuecomment-48561073
  
    +1


> Kafka spout: throw RuntimeException if a leader cannot be found for a partition
> -------------------------------------------------------------------------------
>
>                 Key: STORM-380
>                 URL: https://issues.apache.org/jira/browse/STORM-380
>             Project: Apache Storm (Incubating)
>          Issue Type: Improvement
>            Reporter: Stephen Elliott
>            Priority: Minor
>
> If one of the partitions of the Kafka queue has no leader available, DynamicBrokersReader.getLeaderFor(partition)
returns -1. This is logged in DynamicBrokersReader.getBrokerInfo (as there's no ZK node for
a broker id -1) but there is no further action.
> In this situation the spout will carry on emitting only for those partitions that are
available.
> My assumption is that if some partitions for a queue are unavailable, there's a problem
that needs to be addressed before processing continues. Happy to discuss further.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message