You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/05/04 18:47:04 UTC

[jira] [Resolved] (KAFKA-5118) Improve message for Kafka failed startup with non-Kafka data in data.dirs

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

Guozhang Wang resolved KAFKA-5118.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0.0

Issue resolved by pull request 2907
[https://github.com/apache/kafka/pull/2907]

> Improve message for Kafka failed startup with non-Kafka data in data.dirs
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-5118
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5118
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.10.2.0
>            Reporter: Dustin Cote
>            Assignee: huxi
>            Priority: Minor
>             Fix For: 0.11.0.0
>
>
> Today, if you try to startup a broker with some non-Kafka data in the data.dirs you end up with a cryptic message:
> {code}
> [2017-04-21 13:35:08,122] ERROR There was an error in one of the threads during logs loading: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 (kafka.log.LogManager) 
> [2017-04-21 13:35:08,124] FATAL [Kafka Server 3], Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer) 
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1 
> {code}
> It'd be better if we could tell the user to look for non-Kafka data in the data.dirs and print out the offending directory that caused the problem in the first place.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)