[
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 Producer
[
https://issues.apache.org/jira/browse/KAFKA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638656#comment-14638656
]
Kostya Golikov commented on KAFKA-2352:
---
Indeed, the problem was caused by upstream
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
[
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 July 7th
[
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
Possible
I've skimmed through a source code of Mirror Maker and I see that it relies
on raw threads
https://github.com/apache/kafka/blob/7df39e0394a6fd2f26e8f12768ebf7fecd56e3da/core/src/main/scala/kafka/tools/MirrorMaker.scala#L285-L287,
as opposed to Runnable + Thread pool combination. While former
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: Kafka
[
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.handler
[
https://issues.apache.org/jira/browse/KAFKA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049204#comment-14049204
]
Kostya Golikov commented on KAFKA-1419:
---
[~joestein], Scala 2.11 is only *source
Why not use *scala*doc then? It is way prettier than javadoc
2014-01-30 Jay Kreps jay.kr...@gmail.com:
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.
[
https://issues.apache.org/jira/browse/KAFKA-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869538#comment-13869538
]
Kostya Golikov commented on KAFKA-1197:
---
Is it really an issue to sum up offsets
...@gmail.com
Yeah sure... i have attached the pom.xml. storm-starter is my project. In
fact it is storm project. Hence certain dependencies are relate to storm.
Ans i have included kafka's too since my code contains both storm and kafka
API.
--Padma Ch
On Wed, Dec 18, 2013 at 12:51 PM, Kostya
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 padmapriy...@gmail.com
Hi All,
I am using kafka 0.8.0-beta1 on windows. In the maven project i included
kafka dependencies
[
https://issues.apache.org/jira/browse/KAFKA-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846367#comment-13846367
]
Kostya Golikov commented on KAFKA-1171:
---
[~mumrah] talking about sbt pros
[
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
[
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)
From
[
https://issues.apache.org/jira/browse/KAFKA-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13842833#comment-13842833
]
Kostya Golikov commented on KAFKA-1173:
---
I think it is important to notice somewhere
[
https://issues.apache.org/jira/browse/KAFKA-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13838763#comment-13838763
]
Kostya Golikov commented on KAFKA-1166:
---
Duplicate of https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/KAFKA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13838769#comment-13838769
]
Kostya Golikov commented on KAFKA-1165:
---
If you talking about slash
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
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 mdma...@gmail.com
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
[
https://issues.apache.org/jira/browse/KAFKA-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817354#comment-13817354
]
Kostya Golikov commented on KAFKA-1128:
---
Actually you don't need to create any
[
https://issues.apache.org/jira/browse/KAFKA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804004#comment-13804004
]
Kostya Golikov commented on KAFKA-1079:
---
1. It is common convention in Scala
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 mum...@gmail.com
I've
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
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/KAFKA
26 matches
Mail list logo
