[jira] [Resolved] (KAFKA-2352) Possible memory leak in MirrorMaker and/or new Producer

[ https://issues.apache.org/jira/browse/KAFKA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov resolved KAFKA-2352. --- Resolution: Not A Problem > Possible memory leak in MirrorMaker and/or new Produ

[jira] [Commented] (KAFKA-2352) Possible memory leak in MirrorMaker and/or new Producer

[ https://issues.apache.org/jira/browse/KAFKA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638656#comment-14638656 ] Kostya Golikov commented on KAFKA-2352: --- Indeed, the problem was caused by upst

[jira] [Updated] (KAFKA-2352) Possible memory leak in MirrorMaker and/or new Producer

[ https://issues.apache.org/jira/browse/KAFKA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-2352: -- Attachment: producer.conf consumer.conf output.log > Possi

[jira] [Updated] (KAFKA-2352) Possible memory leak in MirrorMaker and/or new Producer

[ https://issues.apache.org/jira/browse/KAFKA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-2352: -- Description: I've been playing around with Mirror Maker (version from trunk, dated Jul

[jira] [Created] (KAFKA-2352) Possible memory leak in MirrorMaker and/or new Producer

Kostya Golikov created KAFKA-2352: - Summary: Possible memory leak in MirrorMaker and/or new Producer Key: KAFKA-2352 URL: https://issues.apache.org/jira/browse/KAFKA-2352 Project: Kafka

How "low-level" management of threads is justified in Mirror Maker?

I've skimmed through a source code of Mirror Maker and I see that it relies on raw threads , as opposed to "Runnable + Thread pool" combination. While former ap

[jira] [Updated] (KAFKA-2314) Proper help message for MirrorMaker's `message.handler` property

[ https://issues.apache.org/jira/browse/KAFKA-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-2314: -- Attachment: Replacing_copy-pasted_description_of_`message_handler

[jira] [Updated] (KAFKA-2314) Proper help message for MirrorMaker's `message.handler` property

[ https://issues.apache.org/jira/browse/KAFKA-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-2314: -- Status: Patch Available (was: Open) > Proper help message for MirrorMaker's `message

[jira] [Created] (KAFKA-2314) Proper help message for MirrorMaker's `message.handler` property

Kostya Golikov created KAFKA-2314: - Summary: Proper help message for MirrorMaker's `message.handler` property Key: KAFKA-2314 URL: https://issues.apache.org/jira/browse/KAFKA-2314 Project:

[jira] [Commented] (KAFKA-1419) cross build for scala 2.11

[ https://issues.apache.org/jira/browse/KAFKA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049204#comment-14049204 ] Kostya Golikov commented on KAFKA-1419: --- [~joestein], Scala 2.11 is only *so

Re: Published Java/Scala docs?

Why not use *scala*doc then? It is way prettier than javadoc 2014-01-30 Jay Kreps : > The primary problem was that we never found a way to get sane javadocs for > scala code. Moving the clients out of scala will fix this (e.g. > > http://empathybox.com/kafka-javadoc/index.html?kafka/clients/prod

[jira] [Commented] (KAFKA-1197) Count of bytes or messages of a topic stored in kafka

[ https://issues.apache.org/jira/browse/KAFKA-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869538#comment-13869538 ] Kostya Golikov commented on KAFKA-1197: --- Is it really an issue to sum up off

Re: Issue in kafka dependency

t; --Padma Ch > > > On Wed, Dec 18, 2013 at 12:51 PM, Kostya Golikov > wrote: > >> Can you show us resulting pom? As far as I can judge, there is no >> storm-starter in kafka dependencies, unless it is somehow transitive. >> >> >> 2013/12/18 padma priya

Re: Issue in kafka dependency

Can you show us resulting pom? As far as I can judge, there is no storm-starter in kafka dependencies, unless it is somehow transitive. 2013/12/18 padma priya chitturi > Hi All, > > I am using kafka 0.8.0-beta1 on windows. In the maven project i included > kafka dependencies from > ( > > http:/

[jira] [Commented] (KAFKA-1171) Gradle build for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846367#comment-13846367 ] Kostya Golikov commented on KAFKA-1171: --- [~mumrah] talking about sbt pros -- i

[jira] [Updated] (KAFKA-1079) Liars in PrimitiveApiTest that promise to test api in compression mode, but don't do this actually

[ https://issues.apache.org/jira/browse/KAFKA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-1079: -- Attachment: testing-with-compression-v2.patch += New version of path with comments addressed

[jira] [Updated] (KAFKA-1079) Liars in PrimitiveApiTest that promise to test api in compression mode, but don't do this actually

[ https://issues.apache.org/jira/browse/KAFKA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-1079: -- Fix Version/s: 0.8.1 Status: Patch Available (was: Open) >F

[jira] [Commented] (KAFKA-1173) Using Vagrant to get up and running with Apache Kafka

[ https://issues.apache.org/jira/browse/KAFKA-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842833#comment-13842833 ] Kostya Golikov commented on KAFKA-1173: --- I think it is important to no

[jira] [Commented] (KAFKA-1165) typo in kafka-server-stop.sh

[ https://issues.apache.org/jira/browse/KAFKA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838769#comment-13838769 ] Kostya Golikov commented on KAFKA-1165: --- If you talking about slash -- it is n

[jira] [Commented] (KAFKA-1166) typo in kafka-server-stop.sh

[ https://issues.apache.org/jira/browse/KAFKA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838763#comment-13838763 ] Kostya Golikov commented on KAFKA-1166: --- Duplicate of https://issues.apache

Re: [VOTE] Apache Kafka Release 0.8.0 - Candidate 5

Talking about binary release, do we really need to include bin/run-rat.sh? As far as I understand it is only used to bring licenses to the scene and quite redundant for already baked release. Next, I not quite sure, but probably it makes sense to drop libs/scala-compiler.jar -- kafka do not perfor

Re: Auto create "chroot" on server start up?

Just one word: Windows. I'm not a maintainer, but AFAIK kafka targets Windows as well and isn't chroot is a Unix-specific feature? 2013/11/14 marek > Hey, > > I'm trying to feel-out if auto creating the broker's registration path > on server start up would be wanted as a code contribution. > >

[jira] [Commented] (KAFKA-1128) Github is still showing 0.7 as the default branch

[ https://issues.apache.org/jira/browse/KAFKA-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817354#comment-13817354 ] Kostya Golikov commented on KAFKA-1128: --- Actually you don't need to c

[jira] [Commented] (KAFKA-1079) Liars in PrimitiveApiTest that promise to test api in compression mode, but don't do this actually

[ https://issues.apache.org/jira/browse/KAFKA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804004#comment-13804004 ] Kostya Golikov commented on KAFKA-1079: --- 1. It is common convention in Scal

[jira] [Updated] (KAFKA-1079) Liars in PrimitiveApiTest that promise to test api in compression mode, but don't do this actually

[ https://issues.apache.org/jira/browse/KAFKA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-1079: -- Attachment: testing-with-compression-producer.patch Late patch for an issue. I also did a

Re: Warnings in IntelliJ

This usually happens when you have misconfigured java sdk. If you will go to the project settings you will likely see something like this: http://take.ms/ZtaeO9 Try to switch it to a proper sdk and errors should go away: http://take.ms/3hvfits 2013/10/23 David Arthur > I've just imported Kafka

[jira] [Updated] (KAFKA-1079) Liars in PrimitiveApiTest that promise to test api in compression mode, but don't do this actually

[ https://issues.apache.org/jira/browse/KAFKA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kostya Golikov updated KAFKA-1079: -- Description: Long time ago (0.7) we had ByteBufferMessageSet as a part of api and it&#

[jira] [Created] (KAFKA-1079) Liars in PrimitiveApiTest that promise to test api in compression mode, but don't do this actually

Kostya Golikov created KAFKA-1079: - Summary: Liars in PrimitiveApiTest that promise to test api in compression mode, but don't do this actually Key: KAFKA-1079 URL: https://issues.apache.org/jira/browse/

Why JUnit3?

Hi, kafka team and all! Is there anything that stops kafka from moving to scalatest completely? It is supported by major IDE players (IDEA, Eclipse plugin) and pretty mature atm. Alternatively we could just bump to junit4, if we're not ready to be completely scalish. If you concerned about change