You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ashish Kumar Singh (JIRA)" <ji...@apache.org> on 2014/12/02 01:12:12 UTC
[jira] [Commented] (KAFKA-742) Existing directories under the Kafka
data directory without any data cause process to not start
[ https://issues.apache.org/jira/browse/KAFKA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230737#comment-14230737 ]
Ashish Kumar Singh commented on KAFKA-742:
------------------------------------------
[~jkreps], [~chriscurtin], I would like to take a stab at this. Assigning it to myself.
> Existing directories under the Kafka data directory without any data cause process to not start
> -----------------------------------------------------------------------------------------------
>
> Key: KAFKA-742
> URL: https://issues.apache.org/jira/browse/KAFKA-742
> Project: Kafka
> Issue Type: Bug
> Components: config
> Affects Versions: 0.8.0
> Reporter: Chris Curtin
> Assignee: Ashish Kumar Singh
>
> I incorrectly setup the configuration file to have the metrics go to /var/kafka/metrics while the logs were in /var/kafka. On startup I received the following error then the daemon exited:
> 30 [main] INFO kafka.log.LogManager - [Log Manager on Broker 0] Loading log 'metrics'
> 32 [main] FATAL kafka.server.KafkaServerStartable - Fatal error during KafkaServerStable startup. Prepare to shutdown
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1937)
> at kafka.log.LogManager.kafka$log$LogManager$$parseTopicPartitionName(LogManager.scala:335)
> at kafka.log.LogManager$$anonfun$loadLogs$1$$anonfun$apply$3.apply(LogManager.scala:112)
> at kafka.log.LogManager$$anonfun$loadLogs$1$$anonfun$apply$3.apply(LogManager.scala:109)
> at scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:34)
> at scala.collection.mutable.ArrayOps.foreach(ArrayOps.scala:34)
> at kafka.log.LogManager$$anonfun$loadLogs$1.apply(LogManager.scala:109)
> at kafka.log.LogManager$$anonfun$loadLogs$1.apply(LogManager.scala:101)
> at scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:34)
> at scala.collection.mutable.WrappedArray.foreach(WrappedArray.scala:32)
> at kafka.log.LogManager.loadLogs(LogManager.scala:101)
> at kafka.log.LogManager.<init>(LogManager.scala:62)
> at kafka.server.KafkaServer.startup(KafkaServer.scala:59)
> at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:34)
> at kafka.Kafka$.main(Kafka.scala:46)
> at kafka.Kafka.main(Kafka.scala)
> 34 [main] INFO kafka.server.KafkaServer - [Kafka Server 0], shutting down
> This was on a brand new cluster so no data or metrics logs existed yet.
> Moving the metrics to their own directory (not a child of the logs) allowed the daemon to start.
> Took a few minutes to figure out what was wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)