Re: Please clean your ZK and Kafka data if you check out 0.8 HEAD

Is it possible to upgrade one without upgrading the other? I did a git pull, ./sbt update package. Then for kicks I did sbt clean package, just to be sure. ben

Re: Please clean your ZK and Kafka data if you check out 0.8 HEAD

Sorry, I should have clarified something -- using the normal ConsoleConsumer does *not* produce this error. So something in my formatter, or in the logic of a custom formatter must change? ben

Re: Please clean your ZK and Kafka data if you check out 0.8 HEAD

Hi Swapnil, I have done exactly this (killed and wiped everything), and have found that my custom formatter based ConsoleConsumer fails: [2013-02-27 12:34:31,420] ERROR Error processing message, stopping consumer: (kafka.consumer.ConsoleConsumer$) java.lang.NumberFormatException: For input strin

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13569320#comment-13569320 ] ben fleis commented on KAFKA-736: - This is more-or-less what my node command line

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13569294#comment-13569294 ] ben fleis commented on KAFKA-736: - Went back and tested the 'draft' patch, a

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13568192#comment-13568192 ] ben fleis commented on KAFKA-736: - I tried the v2 patch linked above this morning aga

[jira] [Created] (KAFKA-706) broker appears to be encoding ProduceResponse, but never sending it

ben fleis created KAFKA-706: --- Summary: broker appears to be encoding ProduceResponse, but never sending it Key: KAFKA-706 URL: https://issues.apache.org/jira/browse/KAFKA-706 Project: Kafka Issue

[jira] [Created] (KAFKA-704) ConsumerFetcherThread can create illegal clientId

ben fleis created KAFKA-704: --- Summary: ConsumerFetcherThread can create illegal clientId Key: KAFKA-704 URL: https://issues.apache.org/jira/browse/KAFKA-704 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-692) ConsoleConsumer outputs diagnostic message to stdout instead of stderr

[ https://issues.apache.org/jira/browse/KAFKA-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552214#comment-13552214 ] ben fleis commented on KAFKA-692: - Agreed - I just patched it so it didn't get

[jira] [Updated] (KAFKA-692) ConsoleConsumer outputs diagnostic message to stdout instead of stderr

[ https://issues.apache.org/jira/browse/KAFKA-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ben fleis updated KAFKA-692: Description: At the end of its handling loop, ConsoleConsumer prints "Consumed %d messages" t

[jira] [Issue Comment Deleted] (KAFKA-692) ConsoleConsumer outputs diagnostic message to stdout instead of stderr

[ https://issues.apache.org/jira/browse/KAFKA-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ben fleis updated KAFKA-692: Comment: was deleted (was: from stdout -> stderr) > ConsoleConsumer outputs diagnostic mess

[jira] [Updated] (KAFKA-692) ConsoleConsumer outputs diagnostic message to stdout instead of stderr

[ https://issues.apache.org/jira/browse/KAFKA-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ben fleis updated KAFKA-692: Attachment: kafka_692_v1.diff stdout -> stderr > ConsoleConsumer outputs diag

[jira] [Updated] (KAFKA-692) ConsoleConsumer outputs diagnostic message to stdout instead of stderr

[ https://issues.apache.org/jira/browse/KAFKA-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ben fleis updated KAFKA-692: Status: Patch Available (was: Open) from stdout -> stderr > ConsoleConsumer o

[jira] [Created] (KAFKA-692) ConsoleConsumer outputs diagnostic message to stdout instead of stderr

ben fleis created KAFKA-692: --- Summary: ConsoleConsumer outputs diagnostic message to stdout instead of stderr Key: KAFKA-692 URL: https://issues.apache.org/jira/browse/KAFKA-692 Project: Kafka

[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven repository

[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549515#comment-13549515 ] ben fleis commented on KAFKA-133: - I'm new to maven, so this may be a dumb questi

[jira] [Commented] (KAFKA-689) Can't append to a topic/partition that does not already exist

[ https://issues.apache.org/jira/browse/KAFKA-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549500#comment-13549500 ] ben fleis commented on KAFKA-689: - Although it's not precisely the same, perhaps

Re: order guarantee failure: better/best effort?

Heey Jy, Any luck with a java triggering test? b

Re: Splitting client code

As a somewhat related follow up, what are the team's intentions wrt releasing jar files, period? I see source tarballs, but no precompiled, ready-to-run jars in the download section. Is this in the roadmap, easily obtained, etc? For some deployment (like mine, where my client is in another langu

unfortunate test -- delete me

testing mailing list funk, sorry. ben

Re: order guarantee failure: better/best effort?

Hey Jay, (yes, I just like the sound of that!) I have a testing harness for my Node client, but I can't (at the moment) put it out in the open. If you'd like, I cab share it via LI channels and get you into full simulation without too much pain, I think. And yes, they are same partition, same s

order guarantee failure: better/best effort?

Hello all, While running my own system tests against 0.8/HEAD, I was seeing repeated ordering failures, and tracked it down a bit further. In simple summary, I am sending out 2 consecutive ProduceRequests, X and Y. Y gets written to disk before X. Consumer sees Y before X. Bug #382

order guarantee failure: better/best effort?

Hello all, While running my own system tests against 0.8/HEAD, I was seeing repeated ordering failures, and tracked it down a bit further. In simple summary, I am sending out 2 consecutive ProduceRequests, X and Y. Y gets written to disk before X. Consumer sees Y before X. Bug #382

Re: 0.8 Protocol Status

I haven't gone back to check the code, but it feels like every size that's given can be used to verify how to proceed. In the case I was having, 200k made no sense because there wasn't 200k worth of data to write, but the system still flushed the message out to disk, presumably due to using an ear

Re: 0.8 Protocol Status

Neha, thanks for the tip. Useful util! My problem was simple -- I missed one of the size field changes in the producer, which led to a completely wrong size field. Am I correct in believing that the broker doesn't sanity check the message size field against the received data? In this case, the

Re: 0.8 Protocol Status

I was testing my own code, and using the console consumer against my seemingly-working-producer code. Since the last update, the console consumer crashes. I am going to try to track it down in the debugger and will come back with a patch if found. Command line: KAFKA_OPTS="-Xmx512M -server -Dlog

Re: 0.8/HEAD Console consumer breakage?

Dah. Misfire. Please ignore if this makes it to an inbox ;) -b On Fri, Dec 7, 2012 at 4:13 PM, ben fleis wrote: > So I was testing my own code, and using the console consumer against my > seemingly-working-producer code. Since the last update, the console > consumer crashes. I

0.8/HEAD Console consumer breakage?

So I was testing my own code, and using the console consumer against my seemingly-working-producer code. Since the last update, the console consumer crashes. I am going to try to track it down in the debugger and will come back with a patch if found.