You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/09/26 04:42:04 UTC

[jira] [Updated] (STORM-380) Kafka spout: throw RuntimeException if a leader cannot be found for a partition

     [ https://issues.apache.org/jira/browse/STORM-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-380:
-------------------------------
    Component/s: storm-kafka

> 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
>          Issue Type: Improvement
>          Components: storm-kafka
>            Reporter: Stephen Elliott
>            Assignee: Stephen Elliott
>            Priority: Minor
>             Fix For: 0.9.3
>
>
> 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.3.4#6332)