[jira] [Commented] (KAFKA-682) java.lang.OutOfMemoryError: Java heap space

[ https://issues.apache.org/jira/browse/KAFKA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545344#comment-13545344 ] Ricky Ng-Adam commented on KAFKA-682: - After filing the bug initially, I switched to th

[jira] [Updated] (KAFKA-682) java.lang.OutOfMemoryError: Java heap space

[ https://issues.apache.org/jira/browse/KAFKA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ricky Ng-Adam updated KAFKA-682: Attachment: java_pid22281_Leak_Suspects.zip java_pid22281.hprof.gz the hprof dump

Re: kafka mavenification

>> Where do we feel we are with 0.8 ? We can release a public beta by the end of the month, but we are still few weeks away from announcing a release. Thanks, Neha On Sat, Jan 5, 2013 at 10:50 PM, Joe Stein wrote: > Where do we feel we are with 0.8 ?

Re: kafka mavenification

Ok, I will commit this patch then just to trunk and we can have the 0.8 beta mavenized. That works! /* Joe Stein, Chief Architect http://www.medialets.com Twitter: @allthingshadoop Mobile: 917-597-9771 */ On Jan 6, 2013, at 1:31 PM, Neha Narkhede wrote: >>> Where do we feel we are with 0.8 ?

[jira] [Updated] (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:all-tabpanel ] Joe Stein updated KAFKA-133: Resolution: Fixed Status: Resolved (was: Patch Available) I committed this with 2 minor changes 1

[jira] [Commented] (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?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545633#comment-13545633 ] Neha Narkhede commented on KAFKA-621: - Can we check if this is still a problem ?

About Kafka 0.8 producer

Hi all, I find that in Kafka 0.72, we can specify either zk.connect or broker.list. But in Kafka 0.8, we can only specify broker.list ,and we can't specify zk.connect without specifying broker.list. I think, in this case, we can't balance producer through zookeeper. If anyone use Kafka 0.

Kafka 0.8 producer can't specify zk.connect without specifying broker.list

Hi all, I find that in Kafka 0.72, we can specify either zk.connect or broker.list. But in Kafka 0.8, we can only specify broker.list ,and we can't specify zk.connect without specifying broker.list. I think, in this case, we can't balance producer through zookeeper. If anyone use Kafka 0.

Re: git workflow

Although I haven't contributed much here yet, I did want to ask: why diff/patch and not pull/merge? I know my work on getting the SBT build working with a modern SBT was quite a headache for everyone because the diff format was unable to convey things like "delete this binary file and add this othe

Re: About Kafka 0.8 producer

In 0.8, the producer load balances data across the Kafka brokers using a special getMetadata API. You still need to wire in a broker.list since the producer will use this list to talk to one of the brokers to get the leadership information for a new topic/partition. If the leader moves over time, t