[ https://issues.apache.org/jira/browse/STORM-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281585#comment-15281585 ]
B Anil Kumar commented on STORM-1065: ------------------------------------- Hi [~cache007] I just commented on [Storm-380|https://issues.apache.org/jira/browse/STORM-380] Is it possible to include configuration as suggested by [~f.visconte] to allow a mode where offline partition are logged as warning and re-integrated in next ZkCoordinator.refresh() instead of failing whole topology. > storm-kafka : kafka-partition can not find leader in zookeeper > --------------------------------------------------------------- > > Key: STORM-1065 > URL: https://issues.apache.org/jira/browse/STORM-1065 > Project: Apache Storm > Issue Type: Improvement > Components: storm-kafka > Reporter: dongxinwang > Priority: Minor > > If the Kafka cluster is not consistent with the zookeeper data, the partition > can not find leader in zookeeper.In storm-kafka, it throws runtime > exception"No leader found for partition",it is not friendly. > Suggestion: > If there is no leader partition in zookeeper,don't add the partition to > GlobalPartitionInformation object,instead of throwing runtime exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)