[jira] [Created] (KAFKA-876) Produce request: Leader not local for partition [test,0] on broker 0
Yin Yin created KAFKA-876: - Summary: Produce request: Leader not local for partition [test,0] on broker 0 Key: KAFKA-876 URL: https://issues.apache.org/jira/browse/KAFKA-876 Project: Kafka Issue Type: Bug Components: clients, replication Affects Versions: 0.8 Environment: Windows Reporter: Yin Yin Assignee: Neha Narkhede Priority: Blocker Follow the quick start to open zookeeper, one broker, one producer and one consumer. In the producer console, there is an LeaderNotAvailableException for the first message, and the broker complains Produce request: Leader not local for partition [test,0] on broker 0 for all following messages. Kafka-List-Topic shows [2013-04-25 10:21:24,689] INFO zookeeper state changed (SyncConnected) (org.I0Itec.zkclient.ZkClient) topic: test partition: 0 leader: 0 replicas: 0 isr: 0. With --unavailable-partitions option, it doesn't list any topic. =Broker Log= Set JMX_PORT to default value : C:\Projects\Kafka\kafka\bin\.. log4j:ERROR Failed to rename [server.log] to [server.log.2013-04-25-09]. [2013-04-25 10:08:49,531] INFO Verifying properties (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property socket.send.buffer.bytes is overridden to 1048576 (kafka.utils.VerifiablePropert ies) [2013-04-25 10:08:49,578] INFO Property socket.request.max.bytes is overridden to 104857600 (kafka.utils.VerifiablePrope rties) [2013-04-25 10:08:49,578] INFO Property log.dir is overridden to /tmp/kafka-logs (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.cleanup.interval.mins is overridden to 1 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.retention.hours is overridden to 168 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property num.io.threads is overridden to 2 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property broker.id is overridden to 0 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] WARN Property kafka.csv.metrics.reporter.enabled is not valid (kafka.utils.VerifiablePropertie s) [2013-04-25 10:08:49,578] INFO Property port is overridden to 9092 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.flush.interval.messages is overridden to 1 (kafka.utils.VerifiableProper ties) [2013-04-25 10:08:49,578] INFO Property zk.connection.timeout.ms is overridden to 100 (kafka.utils.VerifiablePropert ies) [2013-04-25 10:08:49,578] WARN Property kafka.metrics.reporters is not valid (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] WARN Property kafka.csv.metrics.dir is not valid (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.flush.interval.ms is overridden to 1000 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] WARN Property kafka.metrics.polling.interval.secs is not valid (kafka.utils.VerifiableProperti es) [2013-04-25 10:08:49,578] INFO Property num.network.threads is overridden to 2 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property socket.receive.buffer.bytes is overridden to 1048576 (kafka.utils.VerifiableProp erties) [2013-04-25 10:08:49,578] INFO Property log.segment.bytes is overridden to 536870912 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property zk.connect is overridden to localhost:2181 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,594] INFO Property num.partitions is overridden to 1 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,609] INFO [Kafka Server 0], starting (kafka.server.KafkaServer) [2013-04-25 10:08:49,625] INFO [Log Manager on Broker 0] Log directory 'C:\tmp\kafka-logs' not found, creating it. (kafk a.log.LogManager) [2013-04-25 10:08:49,625] INFO [Log Manager on Broker 0] Starting log cleaner every 6 ms (kafka.log.LogManager) [2013-04-25 10:08:49,640] INFO [Log Manager on Broker 0] Starting log flusher every 3000 ms with the following overrides Map() (kafka.log.LogManager) [2013-04-25 10:08:49,656] INFO Awaiting socket connections on 0.0.0.0:9092. (kafka.network.Acceptor) [2013-04-25 10:08:49,656] INFO [Socket Server on Broker 0], started (kafka.network.SocketServer) [2013-04-25 10:08:49,672] INFO connecting to ZK: localhost:2181 (kafka.server.KafkaZooKeeper) [2013-04-25 10:08:49,672] INFO Starting ZkClient event thread. (org.I0Itec.zkclient.ZkEventThread) [2013-04-25 10:08:49,672] INFO Client environment:zookeeper.version=3.3.3-1203054, built on 11/17/2011 05:47 GMT (org.ap ache.zookeeper.ZooKeeper) [2013-04-25 10:08:49,672] INFO Client environment:host.name=YIYIN-MAIN.redmond.corp.microsoft.com (org.apache.zookeeper. ZooKeeper) [2013-04-25 10:08:49,672] INFO Client environment:java.version=1.7.0_21
[jira] Subscription: outstanding kafka patches
Issue Subscription Filter: outstanding kafka patches (66 issues) The list of outstanding kafka patches Subscriber: kafka-mailing-list Key Summary KAFKA-873 Consider replacing zkclient with curator (with zkclient-bridge) https://issues.apache.org/jira/browse/KAFKA-873 KAFKA-871 Rename ZkConfig properties https://issues.apache.org/jira/browse/KAFKA-871 KAFKA-868 System Test - add test case for rolling controlled shutdown https://issues.apache.org/jira/browse/KAFKA-868 KAFKA-863 System Test - update 0.7 version of kafka-run-class.sh for Migration Tool test cases https://issues.apache.org/jira/browse/KAFKA-863 KAFKA-860 Replica fetcher thread errors out and dies during rolling bounce of cluster https://issues.apache.org/jira/browse/KAFKA-860 KAFKA-859 support basic auth protection of mx4j console https://issues.apache.org/jira/browse/KAFKA-859 KAFKA-856 Correlation id for OffsetFetch request (#2) always responds with 0 https://issues.apache.org/jira/browse/KAFKA-856 KAFKA-855 Ant+Ivy build for Kafka https://issues.apache.org/jira/browse/KAFKA-855 KAFKA-854 Upgrade dependencies for 0.8 https://issues.apache.org/jira/browse/KAFKA-854 KAFKA-852 Remove clientId from OffsetFetchResponse and OffsetCommitResponse https://issues.apache.org/jira/browse/KAFKA-852 KAFKA-836 Update quickstart for Kafka 0.8 https://issues.apache.org/jira/browse/KAFKA-836 KAFKA-835 Update 0.8 configs on the website https://issues.apache.org/jira/browse/KAFKA-835 KAFKA-815 Improve SimpleConsumerShell to take in a max messages config option https://issues.apache.org/jira/browse/KAFKA-815 KAFKA-808 Migration tool internal queue between consumer and producer threads should be configurable https://issues.apache.org/jira/browse/KAFKA-808 KAFKA-745 Remove getShutdownReceive() and other kafka specific code from the RequestChannel https://issues.apache.org/jira/browse/KAFKA-745 KAFKA-739 Handle null values in Message payload https://issues.apache.org/jira/browse/KAFKA-739 KAFKA-735 Add looping and JSON output for ConsumerOffsetChecker https://issues.apache.org/jira/browse/KAFKA-735 KAFKA-733 Fat jar option for build, or override for ivy cache location https://issues.apache.org/jira/browse/KAFKA-733 KAFKA-717 scala 2.10 build support https://issues.apache.org/jira/browse/KAFKA-717 KAFKA-705 Controlled shutdown doesn't seem to work on more than one broker in a cluster https://issues.apache.org/jira/browse/KAFKA-705 KAFKA-686 0.8 Kafka broker should give a better error message when running against 0.7 zookeeper https://issues.apache.org/jira/browse/KAFKA-686 KAFKA-682 java.lang.OutOfMemoryError: Java heap space https://issues.apache.org/jira/browse/KAFKA-682 KAFKA-677 Retention process gives exception if an empty segment is chosen for collection https://issues.apache.org/jira/browse/KAFKA-677 KAFKA-674 Clean Shutdown Testing - Log segments checksums mismatch https://issues.apache.org/jira/browse/KAFKA-674 KAFKA-652 Create testcases for clean shut-down https://issues.apache.org/jira/browse/KAFKA-652 KAFKA-649 Cleanup log4j logging https://issues.apache.org/jira/browse/KAFKA-649 KAFKA-645 Create a shell script to run System Test with DEBUG details and tee console output to a file https://issues.apache.org/jira/browse/KAFKA-645 KAFKA-637 Separate log4j environment variable from KAFKA_OPTS in kafka-run-class.sh https://issues.apache.org/jira/browse/KAFKA-637 KAFKA-621 System Test 9051 : ConsoleConsumer doesn't receives any data for 20 topics but works for 10 https://issues.apache.org/jira/browse/KAFKA-621 KAFKA-607 System Test Transient Failure (case 4011 Log Retention) - ConsoleConsumer receives less data https://issues.apache.org/jira/browse/KAFKA-607 KAFKA-606 System Test Transient Failure (case 0302 GC Pause) - Log segments mismatched across replicas https://issues.apache.org/jira/browse/KAFKA-606 KAFKA-598 decouple fetch size from max message size https://issues.apache.org/jira/browse/KAFKA-598 KAFKA-583 SimpleConsumerShell may receive less data inconsistently https://issues.apache.org/jira/browse/KAFKA-583 KAFKA-552 No error messages logged for those failing-to-send messages from Producer https://issues.apache.org/jira/browse/KAFKA-552 KAFKA-547 The ConsumerStats MBean name should include the groupid https://issues.apache.org/jira/browse/KAFKA-547 KAFKA-530 kafka.server.KafkaApis: kafka.common.OffsetOutOfRangeException https://issues.apache.org/jira/browse/KAFKA-530 KAFKA-493 High CPU usage on inactive server
kafka pull request: Fix mis-spell in ConsumerConfig.scala
GitHub user MichaelBlume opened a pull request: https://github.com/apache/kafka/pull/4 Fix mis-spell in ConsumerConfig.scala You can merge this pull request into a Git repository by running: $ git pull https://github.com/MichaelBlume/kafka patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/4.patch commit e4ad4f0633eede7d6234bc02b5902e0330791882 Author: Michael Blume m...@loggly.com Date: 2013-04-25T20:59:31Z Fix mis-spell in ConsumerConfig.scala
[jira] [Commented] (KAFKA-816) Reduce noise in Kafka server logs due to NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642334#comment-13642334 ] BalajiSeshadri commented on KAFKA-816: -- Using the below trunk and i still see error happening.Please lets me know if this can be fixed. https://github.com/apache/kafka.git [2013-04-25 16:47:08,924] WARN [console-consumer-24019_MERD7-21964-1366930009136-8b7f9eb7-leader-finder-thread], Failed to add fetcher for [mytopic,0] to broker id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1) kafka.common.NotLeaderForPartitionException at sun.reflect.GeneratedConstructorAccessor1.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at kafka.common.ErrorMapping$.exceptionFor(ErrorMapping.scala:72) at kafka.consumer.SimpleConsumer.earliestOrLatestOffset(SimpleConsumer.scala:163) at kafka.consumer.ConsumerFetcherThread.handleOffsetOutOfRange(ConsumerFetcherThread.scala:61) at kafka.server.AbstractFetcherThread.addPartition(AbstractFetcherThread.scala:167) at kafka.server.AbstractFetcherManager.addFetcher(AbstractFetcherManager.scala:48) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:79) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:75) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.Iterator$class.foreach(Iterator.scala:772) at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:157) at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:190) at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:45) at scala.collection.mutable.HashMap.foreach(HashMap.scala:95) at kafka.consumer.ConsumerFetcherManager$$anon$1.doWork(ConsumerFetcherManager.scala:75) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51) Reduce noise in Kafka server logs due to NotLeaderForPartitionException --- Key: KAFKA-816 URL: https://issues.apache.org/jira/browse/KAFKA-816 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8 Reporter: Neha Narkhede Assignee: Neha Narkhede Priority: Blocker Labels: kafka-0.8, p2 Attachments: kafka-816.patch, kafka-816-v2.patch Original Estimate: 1h Remaining Estimate: 1h NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-877) id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1) kafka.common.NotLeaderForPartitionException
BalajiSeshadri created KAFKA-877: Summary: id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1) kafka.common.NotLeaderForPartitionException Key: KAFKA-877 URL: https://issues.apache.org/jira/browse/KAFKA-877 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Environment: DEV Reporter: BalajiSeshadri Using the below trunk and i still see error happening.Please let us know if this can be fixed. https://github.com/apache/kafka.git [2013-04-25 16:47:08,924] WARN [console-consumer-24019_MERD7-21964-1366930009136-8b7f9eb7-leader-finder-thread], Failed to add fetcher for [mytopic,0] to broker id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1) kafka.common.NotLeaderForPartitionException at sun.reflect.GeneratedConstructorAccessor1.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at kafka.common.ErrorMapping$.exceptionFor(ErrorMapping.scala:72) at kafka.consumer.SimpleConsumer.earliestOrLatestOffset(SimpleConsumer.scala:163) at kafka.consumer.ConsumerFetcherThread.handleOffsetOutOfRange(ConsumerFetcherThread.scala:61) at kafka.server.AbstractFetcherThread.addPartition(AbstractFetcherThread.scala:167) at kafka.server.AbstractFetcherManager.addFetcher(AbstractFetcherManager.scala:48) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:79) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:75) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.Iterator$class.foreach(Iterator.scala:772) at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:157) at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:190) at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:45) at scala.collection.mutable.HashMap.foreach(HashMap.scala:95) at kafka.consumer.ConsumerFetcherManager$$anon$1.doWork(ConsumerFetcherManager.scala:75) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51) We are evaluating Kafka for our new messaging system and we had tough time running in windows. We somehow managed to run 0.8 using cygwin but when we run the console producer/consumer,we are not getting messages from consumer. Please help us to fix this issue,this might not be related but its keeping on throwing this error on consumer side. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-877) Still getting kafka.common.NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BalajiSeshadri updated KAFKA-877: - Summary: Still getting kafka.common.NotLeaderForPartitionException (was: id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1) kafka.common.NotLeaderForPartitionException) Still getting kafka.common.NotLeaderForPartitionException - Key: KAFKA-877 URL: https://issues.apache.org/jira/browse/KAFKA-877 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Environment: DEV Reporter: BalajiSeshadri Using the below trunk and i still see error happening.Please let us know if this can be fixed. https://github.com/apache/kafka.git [2013-04-25 16:47:08,924] WARN [console-consumer-24019_MERD7-21964-1366930009136-8b7f9eb7-leader-finder-thread], Failed to add fetcher for [mytopic,0] to broker id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1) kafka.common.NotLeaderForPartitionException at sun.reflect.GeneratedConstructorAccessor1.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at kafka.common.ErrorMapping$.exceptionFor(ErrorMapping.scala:72) at kafka.consumer.SimpleConsumer.earliestOrLatestOffset(SimpleConsumer.scala:163) at kafka.consumer.ConsumerFetcherThread.handleOffsetOutOfRange(ConsumerFetcherThread.scala:61) at kafka.server.AbstractFetcherThread.addPartition(AbstractFetcherThread.scala:167) at kafka.server.AbstractFetcherManager.addFetcher(AbstractFetcherManager.scala:48) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:79) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:75) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.Iterator$class.foreach(Iterator.scala:772) at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:157) at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:190) at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:45) at scala.collection.mutable.HashMap.foreach(HashMap.scala:95) at kafka.consumer.ConsumerFetcherManager$$anon$1.doWork(ConsumerFetcherManager.scala:75) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51) We are evaluating Kafka for our new messaging system and we had tough time running in windows. We somehow managed to run 0.8 using cygwin but when we run the console producer/consumer,we are not getting messages from consumer. Please help us to fix this issue,this might not be related but its keeping on throwing this error on consumer side. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-877) Still getting kafka.common.NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BalajiSeshadri updated KAFKA-877: - Priority: Blocker (was: Major) Still getting kafka.common.NotLeaderForPartitionException - Key: KAFKA-877 URL: https://issues.apache.org/jira/browse/KAFKA-877 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Environment: DEV Reporter: BalajiSeshadri Priority: Blocker Using the below trunk and i still see error happening.Please let us know if this can be fixed. https://github.com/apache/kafka.git [2013-04-25 16:47:08,924] WARN [console-consumer-24019_MERD7-21964-1366930009136-8b7f9eb7-leader-finder-thread], Failed to add fetcher for [mytopic,0] to broker id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1) kafka.common.NotLeaderForPartitionException at sun.reflect.GeneratedConstructorAccessor1.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at kafka.common.ErrorMapping$.exceptionFor(ErrorMapping.scala:72) at kafka.consumer.SimpleConsumer.earliestOrLatestOffset(SimpleConsumer.scala:163) at kafka.consumer.ConsumerFetcherThread.handleOffsetOutOfRange(ConsumerFetcherThread.scala:61) at kafka.server.AbstractFetcherThread.addPartition(AbstractFetcherThread.scala:167) at kafka.server.AbstractFetcherManager.addFetcher(AbstractFetcherManager.scala:48) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:79) at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:75) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95) at scala.collection.Iterator$class.foreach(Iterator.scala:772) at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:157) at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:190) at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:45) at scala.collection.mutable.HashMap.foreach(HashMap.scala:95) at kafka.consumer.ConsumerFetcherManager$$anon$1.doWork(ConsumerFetcherManager.scala:75) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51) We are evaluating Kafka for our new messaging system and we had tough time running in windows. We somehow managed to run 0.8 using cygwin but when we run the console producer/consumer,we are not getting messages from consumer. Please help us to fix this issue,this might not be related but its keeping on throwing this error on consumer side. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-816) Reduce noise in Kafka server logs due to NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642342#comment-13642342 ] Neha Narkhede commented on KAFKA-816: - All 0.8 development is happening on the 0.8 branch. Please can you retry on that branch ? Reduce noise in Kafka server logs due to NotLeaderForPartitionException --- Key: KAFKA-816 URL: https://issues.apache.org/jira/browse/KAFKA-816 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8 Reporter: Neha Narkhede Assignee: Neha Narkhede Priority: Blocker Labels: kafka-0.8, p2 Attachments: kafka-816.patch, kafka-816-v2.patch Original Estimate: 1h Remaining Estimate: 1h NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-816) Reduce noise in Kafka server logs due to NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642344#comment-13642344 ] BalajiSeshadri commented on KAFKA-816: -- Please let me know the Git URL. Reduce noise in Kafka server logs due to NotLeaderForPartitionException --- Key: KAFKA-816 URL: https://issues.apache.org/jira/browse/KAFKA-816 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8 Reporter: Neha Narkhede Assignee: Neha Narkhede Priority: Blocker Labels: kafka-0.8, p2 Attachments: kafka-816.patch, kafka-816-v2.patch Original Estimate: 1h Remaining Estimate: 1h NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (KAFKA-816) Reduce noise in Kafka server logs due to NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642346#comment-13642346 ] BalajiSeshadri edited comment on KAFKA-816 at 4/25/13 11:02 PM: I see fix merged in the show log but it is not working. SHA-1: 51421fcc0111031bb77f779a6f6c00520d526a34 * KAFKA-816 Reduce noise in Kafka server logs due to NotLeaderForPartitionException; reviewed by Jun Rao was (Author: balaji.sesha...@dish.com): I see fix merged in the show log. SHA-1: 51421fcc0111031bb77f779a6f6c00520d526a34 * KAFKA-816 Reduce noise in Kafka server logs due to NotLeaderForPartitionException; reviewed by Jun Rao Reduce noise in Kafka server logs due to NotLeaderForPartitionException --- Key: KAFKA-816 URL: https://issues.apache.org/jira/browse/KAFKA-816 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8 Reporter: Neha Narkhede Assignee: Neha Narkhede Priority: Blocker Labels: kafka-0.8, p2 Attachments: kafka-816.patch, kafka-816-v2.patch Original Estimate: 1h Remaining Estimate: 1h NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-880) NoLeaderPartitionSet should be cleared before leader finder thread is started up
Joel Koshy created KAFKA-880:
Summary: NoLeaderPartitionSet should be cleared before leader
finder thread is started up
Key: KAFKA-880
URL: https://issues.apache.org/jira/browse/KAFKA-880
Project: Kafka
Issue Type: Bug
Affects Versions: 0.8
Reporter: Joel Koshy
Fix For: 0.8
This was a recent regression.
This could prevent the consumer from progressing because fetchers for the
currently owned partitions may not be added (depending on the order that the
map iterator yields).
I think the fix should be simple - just clear the set after stopping the leader
finder thread and stopping fetchers.
{code}
[2013-04-25 17:06:38,377] WARN
[sometopic-somehost-1366909575615-f801367d-leader-finder-thread]
, Failed to find leader for Set([sometopic,11], [sometopic,25], [sometopic,24])
(kafka.consumer.ConsumerFetcherManager$Lead
erFinderThread)
java.util.NoSuchElementException: key not found: [sometopic,24]
at scala.collection.MapLike$class.default(MapLike.scala:223)
at scala.collection.immutable.Map$Map2.default(Map.scala:110)
at scala.collection.MapLike$class.apply(MapLike.scala:134)
at scala.collection.immutable.Map$Map2.apply(Map.scala:110)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:81)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:79)
at
scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
at
scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
at scala.collection.Iterator$class.foreach(Iterator.scala:631)
at
scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:161)
at
scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:194)
at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39)
at scala.collection.mutable.HashMap.foreach(HashMap.scala:80)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:79)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-880) NoLeaderPartitionSet should be cleared before leader finder thread is started up
[
https://issues.apache.org/jira/browse/KAFKA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-880:
-
Description:
This was a recent regression.
This could prevent the consumer from progressing because fetchers for the
currently owned partitions may not be added (depending on the order that the
map iterator yields).
I think the fix should be simple - just clear the set after stopping the leader
finder thread and stopping fetchers.
[2013-04-25 17:06:38,377] WARN
[sometopic-somehost-1366909575615-f801367d-leader-finder-thread]
, Failed to find leader for Set([sometopic,11], [sometopic,25], [sometopic,24])
(kafka.consumer.ConsumerFetcherManager$Lead
erFinderThread)
java.util.NoSuchElementException: key not found: [sometopic,24]
at scala.collection.MapLike$class.default(MapLike.scala:223)
at scala.collection.immutable.Map$Map2.default(Map.scala:110)
at scala.collection.MapLike$class.apply(MapLike.scala:134)
at scala.collection.immutable.Map$Map2.apply(Map.scala:110)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:81)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:79)
at
scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
at
scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
at scala.collection.Iterator$class.foreach(Iterator.scala:631)
at
scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:161)
at
scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:194)
at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39)
at scala.collection.mutable.HashMap.foreach(HashMap.scala:80)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:79)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
was:
This was a recent regression.
This could prevent the consumer from progressing because fetchers for the
currently owned partitions may not be added (depending on the order that the
map iterator yields).
I think the fix should be simple - just clear the set after stopping the leader
finder thread and stopping fetchers.
{code}
[2013-04-25 17:06:38,377] WARN
[sometopic-somehost-1366909575615-f801367d-leader-finder-thread]
, Failed to find leader for Set([sometopic,11], [sometopic,25], [sometopic,24])
(kafka.consumer.ConsumerFetcherManager$Lead
erFinderThread)
java.util.NoSuchElementException: key not found: [sometopic,24]
at scala.collection.MapLike$class.default(MapLike.scala:223)
at scala.collection.immutable.Map$Map2.default(Map.scala:110)
at scala.collection.MapLike$class.apply(MapLike.scala:134)
at scala.collection.immutable.Map$Map2.apply(Map.scala:110)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:81)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:79)
at
scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
at
scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
at scala.collection.Iterator$class.foreach(Iterator.scala:631)
at
scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:161)
at
scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:194)
at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39)
at scala.collection.mutable.HashMap.foreach(HashMap.scala:80)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:79)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
{code}
NoLeaderPartitionSet should be cleared before leader finder thread is started
up
Key: KAFKA-880
URL: https://issues.apache.org/jira/browse/KAFKA-880
Project: Kafka
Issue Type: Bug
Affects Versions: 0.8
Reporter: Joel Koshy
Fix For: 0.8
This was a recent regression.
This could prevent the consumer from progressing because fetchers for the
currently owned partitions may not be added (depending on the order that the
map iterator yields).
I think the fix should be simple - just clear the set after stopping the
leader finder thread and stopping fetchers.
[2013-04-25 17:06:38,377] WARN
[sometopic-somehost-1366909575615-f801367d-leader-finder-thread]
, Failed to find leader for Set([sometopic,11], [sometopic,25],
[sometopic,24])
[jira] [Updated] (KAFKA-880) NoLeaderPartitionSet should be cleared before leader finder thread is started up
[ https://issues.apache.org/jira/browse/KAFKA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-880: -- Attachment: kafka-880.patch Good catch. Attach a patch. NoLeaderPartitionSet should be cleared before leader finder thread is started up Key: KAFKA-880 URL: https://issues.apache.org/jira/browse/KAFKA-880 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Reporter: Joel Koshy Fix For: 0.8 Attachments: kafka-880.patch This was a recent regression. This could prevent the consumer from progressing because fetchers for the currently owned partitions may not be added (depending on the order that the map iterator yields). I think the fix should be simple - just clear the set after stopping the leader finder thread and stopping fetchers. [2013-04-25 17:06:38,377] WARN [sometopic-somehost-1366909575615-f801367d-leader-finder-thread] , Failed to find leader for Set([sometopic,11], [sometopic,25], [sometopic,24]) (kafka.consumer.ConsumerFetcherManager$Lead erFinderThread) java.util.NoSuchElementException: key not found: [sometopic,24] at scala.collection.MapLike$class.default(MapLike.scala:223) at scala.collection.immutable.Map$Map2.default(Map.scala:110) at scala.collection.MapLike$class.apply(MapLike.scala:134) at scala.collection.immutable.Map$Map2.apply(Map.scala:110) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:81) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:79) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80) at scala.collection.Iterator$class.foreach(Iterator.scala:631) at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:161) at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:194) at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39) at scala.collection.mutable.HashMap.foreach(HashMap.scala:80) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:79) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-880) NoLeaderPartitionSet should be cleared before leader finder thread is started up
[ https://issues.apache.org/jira/browse/KAFKA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642500#comment-13642500 ] Neha Narkhede commented on KAFKA-880: - +1 NoLeaderPartitionSet should be cleared before leader finder thread is started up Key: KAFKA-880 URL: https://issues.apache.org/jira/browse/KAFKA-880 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Reporter: Joel Koshy Assignee: Jun Rao Fix For: 0.8 Attachments: kafka-880.patch This was a recent regression. This could prevent the consumer from progressing because fetchers for the currently owned partitions may not be added (depending on the order that the map iterator yields). I think the fix should be simple - just clear the set after stopping the leader finder thread and stopping fetchers. [2013-04-25 17:06:38,377] WARN [sometopic-somehost-1366909575615-f801367d-leader-finder-thread] , Failed to find leader for Set([sometopic,11], [sometopic,25], [sometopic,24]) (kafka.consumer.ConsumerFetcherManager$Lead erFinderThread) java.util.NoSuchElementException: key not found: [sometopic,24] at scala.collection.MapLike$class.default(MapLike.scala:223) at scala.collection.immutable.Map$Map2.default(Map.scala:110) at scala.collection.MapLike$class.apply(MapLike.scala:134) at scala.collection.immutable.Map$Map2.apply(Map.scala:110) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:81) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:79) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80) at scala.collection.Iterator$class.foreach(Iterator.scala:631) at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:161) at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:194) at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39) at scala.collection.mutable.HashMap.foreach(HashMap.scala:80) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:79) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-880) NoLeaderPartitionSet should be cleared before leader finder thread is started up
[ https://issues.apache.org/jira/browse/KAFKA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-880: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the review. Committed to 0.8. NoLeaderPartitionSet should be cleared before leader finder thread is started up Key: KAFKA-880 URL: https://issues.apache.org/jira/browse/KAFKA-880 Project: Kafka Issue Type: Bug Affects Versions: 0.8 Reporter: Joel Koshy Assignee: Jun Rao Fix For: 0.8 Attachments: kafka-880.patch This was a recent regression. This could prevent the consumer from progressing because fetchers for the currently owned partitions may not be added (depending on the order that the map iterator yields). I think the fix should be simple - just clear the set after stopping the leader finder thread and stopping fetchers. [2013-04-25 17:06:38,377] WARN [sometopic-somehost-1366909575615-f801367d-leader-finder-thread] , Failed to find leader for Set([sometopic,11], [sometopic,25], [sometopic,24]) (kafka.consumer.ConsumerFetcherManager$Lead erFinderThread) java.util.NoSuchElementException: key not found: [sometopic,24] at scala.collection.MapLike$class.default(MapLike.scala:223) at scala.collection.immutable.Map$Map2.default(Map.scala:110) at scala.collection.MapLike$class.apply(MapLike.scala:134) at scala.collection.immutable.Map$Map2.apply(Map.scala:110) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:81) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$4.apply(ConsumerFetcherManager.scala:79) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80) at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80) at scala.collection.Iterator$class.foreach(Iterator.scala:631) at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:161) at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:194) at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39) at scala.collection.mutable.HashMap.foreach(HashMap.scala:80) at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:79) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-816) Reduce noise in Kafka server logs due to NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642557#comment-13642557 ] BalajiSeshadri commented on KAFKA-816: -- Error occuring still in 0.8 branch,pls refer screen shot attached. Reduce noise in Kafka server logs due to NotLeaderForPartitionException --- Key: KAFKA-816 URL: https://issues.apache.org/jira/browse/KAFKA-816 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8 Reporter: Neha Narkhede Assignee: Neha Narkhede Priority: Blocker Labels: kafka-0.8, p2 Attachments: KAFKA-816.jpg, kafka-816.patch, kafka-816-v2.patch Original Estimate: 1h Remaining Estimate: 1h NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-816) Reduce noise in Kafka server logs due to NotLeaderForPartitionException
[ https://issues.apache.org/jira/browse/KAFKA-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BalajiSeshadri updated KAFKA-816: - Attachment: KAFKA-816.jpg Reduce noise in Kafka server logs due to NotLeaderForPartitionException --- Key: KAFKA-816 URL: https://issues.apache.org/jira/browse/KAFKA-816 Project: Kafka Issue Type: Bug Components: core Affects Versions: 0.8 Reporter: Neha Narkhede Assignee: Neha Narkhede Priority: Blocker Labels: kafka-0.8, p2 Attachments: KAFKA-816.jpg, kafka-816.patch, kafka-816-v2.patch Original Estimate: 1h Remaining Estimate: 1h NotLeaderForPartitionException is logged at the ERROR level with a full stack trace. But really this is just an informational message on the server when a client with stale metadata sends requests to the wrong leader for a partition. This floods the logs either if there are many clients or few clients sending many topics (migration tool or mirror maker). This should probably be logged at WARN and without the stack trace -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-876) Produce request: Leader not local for partition [test,0] on broker 0
[ https://issues.apache.org/jira/browse/KAFKA-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642573#comment-13642573 ] Jun Rao commented on KAFKA-876: --- Hmm, this is weird. The broker log shows that broker 0 has successfully become the leader of topic test partition 0 after handling the leaderAndIsr request. However, afterwards, it still has the warning Leader not local for partition [test,0]. Wondering if this is somehow a Windows specific issue. Produce request: Leader not local for partition [test,0] on broker 0 - Key: KAFKA-876 URL: https://issues.apache.org/jira/browse/KAFKA-876 Project: Kafka Issue Type: Bug Components: clients, replication Affects Versions: 0.8 Environment: Windows Reporter: Yin Yin Assignee: Neha Narkhede Priority: Blocker Follow the quick start to open zookeeper, one broker, one producer and one consumer. In the producer console, there is an LeaderNotAvailableException for the first message, and the broker complains Produce request: Leader not local for partition [test,0] on broker 0 for all following messages. Kafka-List-Topic shows [2013-04-25 10:21:24,689] INFO zookeeper state changed (SyncConnected) (org.I0Itec.zkclient.ZkClient) topic: test partition: 0leader: 0 replicas: 0 isr: 0. With --unavailable-partitions option, it doesn't list any topic. =Broker Log= Set JMX_PORT to default value : C:\Projects\Kafka\kafka\bin\.. log4j:ERROR Failed to rename [server.log] to [server.log.2013-04-25-09]. [2013-04-25 10:08:49,531] INFO Verifying properties (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property socket.send.buffer.bytes is overridden to 1048576 (kafka.utils.VerifiablePropert ies) [2013-04-25 10:08:49,578] INFO Property socket.request.max.bytes is overridden to 104857600 (kafka.utils.VerifiablePrope rties) [2013-04-25 10:08:49,578] INFO Property log.dir is overridden to /tmp/kafka-logs (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.cleanup.interval.mins is overridden to 1 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.retention.hours is overridden to 168 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property num.io.threads is overridden to 2 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property broker.id is overridden to 0 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] WARN Property kafka.csv.metrics.reporter.enabled is not valid (kafka.utils.VerifiablePropertie s) [2013-04-25 10:08:49,578] INFO Property port is overridden to 9092 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.flush.interval.messages is overridden to 1 (kafka.utils.VerifiableProper ties) [2013-04-25 10:08:49,578] INFO Property zk.connection.timeout.ms is overridden to 100 (kafka.utils.VerifiablePropert ies) [2013-04-25 10:08:49,578] WARN Property kafka.metrics.reporters is not valid (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] WARN Property kafka.csv.metrics.dir is not valid (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property log.flush.interval.ms is overridden to 1000 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] WARN Property kafka.metrics.polling.interval.secs is not valid (kafka.utils.VerifiableProperti es) [2013-04-25 10:08:49,578] INFO Property num.network.threads is overridden to 2 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property socket.receive.buffer.bytes is overridden to 1048576 (kafka.utils.VerifiableProp erties) [2013-04-25 10:08:49,578] INFO Property log.segment.bytes is overridden to 536870912 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,578] INFO Property zk.connect is overridden to localhost:2181 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,594] INFO Property num.partitions is overridden to 1 (kafka.utils.VerifiableProperties) [2013-04-25 10:08:49,609] INFO [Kafka Server 0], starting (kafka.server.KafkaServer) [2013-04-25 10:08:49,625] INFO [Log Manager on Broker 0] Log directory 'C:\tmp\kafka-logs' not found, creating it. (kafk a.log.LogManager) [2013-04-25 10:08:49,625] INFO [Log Manager on Broker 0] Starting log cleaner every 6 ms (kafka.log.LogManager) [2013-04-25 10:08:49,640] INFO [Log Manager on Broker 0] Starting log flusher every 3000 ms with the following overrides Map() (kafka.log.LogManager) [2013-04-25 10:08:49,656] INFO Awaiting socket connections on 0.0.0.0:9092. (kafka.network.Acceptor) [2013-04-25 10:08:49,656] INFO [Socket
