[jira] [Created] (KAFKA-912) [Documentation] 0.8 Quickstart mentions sbt assembly-package-dependency - not needed

Martin Eigenbrodt created KAFKA-912: --- Summary: [Documentation] 0.8 Quickstart mentions sbt assembly-package-dependency - not needed Key: KAFKA-912 URL: https://issues.apache.org/jira/browse/KAFKA-912

[jira] [Created] (KAFKA-913) [Documentation] 0.8 Quickstart mentions sbt assembly-package-dependency - not needed

Martin Eigenbrodt created KAFKA-913: --- Summary: [Documentation] 0.8 Quickstart mentions sbt assembly-package-dependency - not needed Key: KAFKA-913 URL: https://issues.apache.org/jira/browse/KAFKA-913

[jira] [Created] (KAFKA-914) Deadlock between initial rebalance and watcher-triggered rebalances

Joel Koshy created KAFKA-914: Summary: Deadlock between initial rebalance and watcher-triggered rebalances Key: KAFKA-914 URL: https://issues.apache.org/jira/browse/KAFKA-914 Project: Kafka

[jira] [Updated] (KAFKA-901) Kafka server can become unavailable if clients send several metadata requests

[ https://issues.apache.org/jira/browse/KAFKA-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-901: Attachment: kafka-901-followup2.patch I agree. Kept only the 2nd logging message about caching the

[jira] [Commented] (KAFKA-913) [Documentation] 0.8 Quickstart mentions sbt assembly-package-dependency - not needed

[ https://issues.apache.org/jira/browse/KAFKA-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663093#comment-13663093 ] Jun Rao commented on KAFKA-913: --- Did you try this on the latest of the 0.8 branch? What OS

[jira] [Resolved] (KAFKA-912) [Documentation] 0.8 Quickstart mentions sbt assembly-package-dependency - not needed

[ https://issues.apache.org/jira/browse/KAFKA-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-912. --- Resolution: Duplicate [Documentation] 0.8 Quickstart mentions sbt assembly-package-dependency - not

produce request wire format question

In the version 0.8 wire format for a produce request, does a value of -1 still indicate use a random partition as it did for 0.7? Thanks, Dave

[jira] [Commented] (KAFKA-914) Deadlock between initial rebalance and watcher-triggered rebalances

[ https://issues.apache.org/jira/browse/KAFKA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663146#comment-13663146 ] Joel Koshy commented on KAFKA-914: -- One more point: [td3] above does not need to originate

Re: produce request wire format question

I'm looking at the document entitled A Guide to the Kafka Protocol located here: https://cwiki.apache.org/KAFKA/a-guide-to-the-kafka-protocol.html It shows a produce request as containing a number of message sets, which are grouped first by topic and second by partition (a 32-bit integer).

Re: produce request wire format question

Dave, Colin described the producer behavior of picking the partition for a message before it is sent to Kafka broker correctly. However, I'm interested in knowing your use case a little before to see why you would rather have the broker decide the partition? Thanks, Neha On Tue, May 21, 2013

Re: produce request wire format question

In my case, there is a load balancer between the producers and the brokers, so I want the behavior described for the Java client (null key specifies any partition). If the Key field of each individual message specifies the partition to send it to, then I don't understand the purpose of the 32-bit

[jira] [Updated] (KAFKA-914) Deadlock between initial rebalance and watcher-triggered rebalances

[ https://issues.apache.org/jira/browse/KAFKA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-914: - Attachment: KAFKA-914-v1.patch Patch with the mentioned fix. 1 - I added comments with some detail since