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
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
Please can you file a bug describing the problem ?
On Sun, Jan 27, 2013 at 7:55 AM, David Arthur mum...@gmail.com 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
[
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
[
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
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:
[
https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13564030#comment-13564030
]
Jay Kreps commented on KAFKA-695:
-
This is a pretty brilliant catch.
That code should not
