[jira] [Commented] (KAFKA-631) Implement log compaction

[ https://issues.apache.org/jira/browse/KAFKA-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564072#comment-13564072 ] Jun Rao commented on KAFKA-631: --- Thanks for patch v7. Looks good overall. Some comments: 70.

[jira] [Commented] (KAFKA-695) Broker shuts down due to attempt to read a closed index file

[ https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564030#comment-13564030 ] Jay Kreps commented on KAFKA-695: - This is a pretty brilliant catch. That code should not

[jira] [Updated] (KAFKA-736) Add an option to the 0.8 producer to mimic 0.7 producer behavior

[ https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-736: Status: Patch Available (was: In Progress) > Add an option to the 0.8 producer to mimic 0.7 pro

[jira] [Updated] (KAFKA-736) Add an option to the 0.8 producer to mimic 0.7 producer behavior

[ https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-736: Attachment: kafka-736-draft.patch This is a draft patch that changes the behavior of the required.re

[jira] [Commented] (KAFKA-738) correlationId is not set in FetchRequest in AbstractFetcherThread

[ https://issues.apache.org/jira/browse/KAFKA-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563965#comment-13563965 ] Swapnil Ghike commented on KAFKA-738: - Probably because we create a new FetchRequestBui

[jira] [Created] (KAFKA-738) correlationId is not set in FetchRequest in AbstractFetcherThread

Jun Rao created KAFKA-738: - Summary: correlationId is not set in FetchRequest in AbstractFetcherThread Key: KAFKA-738 URL: https://issues.apache.org/jira/browse/KAFKA-738 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-695) Broker shuts down due to attempt to read a closed index file

[ https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-695: -- Attachment: kafka-695.patch I have a theory of what's happening here. What we overlooked is that there is anoth

[jira] [Updated] (KAFKA-695) Broker shuts down due to attempt to read a closed index file

[ https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-695: -- Fix Version/s: 0.8 Status: Patch Available (was: Open) > Broker shuts down due to attempt to rea

Re: Difficulties packaging trunk

Please can you file a bug describing the problem ? On Sun, Jan 27, 2013 at 7:55 AM, David Arthur wrote: > Turns out I was using a ZK chroot in my server.properties and the znode > didn't exist, so kafka.Kafka was returning right away. Strange that there > was no error message though. > > > On 1

Re: Unit test failure stack traces

Hi Neha, did some digging and came accross this. ./sbt set every traceLevel := 10 test we can either document it on our wiki or we can set the trace level to a higher number in build.sbt (i.e. traceLevel := 10) let me know how it goes excerpt from http://www.scala-sbt.org/release/docs/Howto/lo

Re: Difficulties packaging trunk

Turns out I was using a ZK chroot in my server.properties and the znode didn't exist, so kafka.Kafka was returning right away. Strange that there was no error message though. On 1/27/13 9:54 AM, David Arthur wrote: I'm trying to run the latest trunk code. I'm packaging the project as indicate

Difficulties packaging trunk

I'm trying to run the latest trunk code. I'm packaging the project as indicated by the README > ./sbt "+package" which runs fine, but then I try to run ./bin/kafka-server-start.sh, I get Caused by: java.lang.ClassNotFoundException: scala.ScalaObject I have also tried various incarnations of