[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383418#comment-14383418
]
Rajiv Kurian edited comment on KAFKA-2045 at 3/27/15 6:51 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383418#comment-14383418
]
Rajiv Kurian commented on KAFKA-2045:
-
Copying from the email list and expanding here.
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383418#comment-14383418
]
Rajiv Kurian edited comment on KAFKA-2045 at 3/27/15 6:53 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383418#comment-14383418
]
Rajiv Kurian edited comment on KAFKA-2045 at 3/27/15 6:53 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383418#comment-14383418
]
Rajiv Kurian edited comment on KAFKA-2045 at 3/27/15 6:54 AM:
--
[
https://issues.apache.org/jira/browse/KAFKA-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383501#comment-14383501
]
Fabian Lange commented on KAFKA-1351:
-
[~ijuma] thanks for the hint, i will double
[
https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383879#comment-14383879
]
Cotizo sima commented on KAFKA-1817:
I can reproduce the same error. Code:
{code}
+1 for dropping 2.9.x support
Kind regards,
Stevo Slavic.
On Fri, Mar 27, 2015 at 3:20 PM, Ismael Juma mli...@juma.me.uk wrote:
Hi all,
The Kafka build currently includes support for Scala 2.9, which means that
it cannot take advantage of features introduced in Scala 2.10 or depend on
Hi all,
The Kafka build currently includes support for Scala 2.9, which means that
it cannot take advantage of features introduced in Scala 2.10 or depend on
libraries that require it.
This restricts the solutions available while trying to solve existing
issues. I was browsing JIRA looking for
+1. But can we also look at this from the deployment base point view and
find out how many production deployments are still using 2.9? If there is
not any, dropping it is really an easy decision.
Thanks
Sent from my iPhone
On Mar 27, 2015, at 8:21 AM, Ismael Juma mli...@juma.me.uk wrote:
Hi
[
https://issues.apache.org/jira/browse/KAFKA-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384084#comment-14384084
]
Gwen Shapira commented on KAFKA-2044:
-
Updated reviewboard
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32459/
---
(Updated March 27, 2015, 4:22 p.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384242#comment-14384242
]
Joel Koshy commented on KAFKA-1546:
---
Patch looks good. This is another ticket for which
Andrew Pennebaker created KAFKA-2061:
Summary: Offer a --version flag to print the kafka version
Key: KAFKA-2061
URL: https://issues.apache.org/jira/browse/KAFKA-2061
Project: Kafka
On March 26, 2015, 3:54 p.m., Jun Rao wrote:
clients/src/main/java/org/apache/kafka/common/requests/MetadataRequest.java,
lines 49-64
https://reviews.apache.org/r/32459/diff/6/?file=906393#file906393line49
For the error response for MetadataRequest, we want to create one such
[
https://issues.apache.org/jira/browse/KAFKA-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2044:
Attachment: KAFKA-2044_2015-03-27_09:22:28.patch
Support requests and responses from o.a.k.common
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384100#comment-14384100
]
Jay Kreps commented on KAFKA-2045:
--
[~rzidane] I do think a prototype would help show
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384558#comment-14384558
]
Jay Kreps commented on KAFKA-2045:
--
Yeah, as you say, I think bounding memory would still
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384544#comment-14384544
]
Rajiv Kurian commented on KAFKA-2045:
-
[~jkreps] the simple pool of ByteBuffers
+1
Thanks Becket!
On Fri, Mar 27, 2015 at 1:19 PM, Jay Kreps jay.kr...@gmail.com wrote:
+1
Thanks for your patience Jiangjie!
-Jay
On Fri, Mar 27, 2015 at 11:48 AM, Jiangjie Qin j...@linkedin.com.invalid
wrote:
+1
Thanks for your patience Jiangjie!
-Jay
On Fri, Mar 27, 2015 at 11:48 AM, Jiangjie Qin j...@linkedin.com.invalid
wrote:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-15+-+Add+a+close+method+with+a+timeout+in+the+producer
Let us vote again!
Hi folks,
It looks everyone is on the same page but just had different preference.
From what I can tell, it seems the option with least concerns is logging
an error and exiting if when close()/close(timeout) is called from
callback. And we will document it crystal clear.
Just in order to make
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384382#comment-14384382
]
Aditya A Auradkar commented on KAFKA-1546:
--
Updated reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384406#comment-14384406
]
Jun Rao commented on KAFKA-1546:
Since the broker has moved to ConfigDef, we can generate
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31967/
---
(Updated March 27, 2015, 6:58 p.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya A Auradkar updated KAFKA-1546:
-
Attachment: KAFKA-1546_2015-03-27_11:57:56.patch
Automate replica lag tuning
Adding to what Jay said.
The library maintains 1k samples by default. The UniformSample has a long array
so about 8k overhead per histogram. The ExponentiallyDecayingSample (which is
what we use) has a 16 byte overhead per stored sample, so about 16k per
histogram. So 10k histograms (worst
https://cwiki.apache.org/confluence/display/KAFKA/KIP-15+-+Add+a+close+method+with+a+timeout+in+the+producer
Let us vote again!
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384734#comment-14384734
]
Aditya Auradkar commented on KAFKA-1546:
[~junrao] I found references to this
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384620#comment-14384620
]
Aditya Auradkar commented on KAFKA-1546:
[~jjkoshy] Where can I find the html to
Michael Braun created KAFKA-2062:
Summary: Sync Producer, Variable Message Length, Multiple Threads
= Direct memory overuse
Key: KAFKA-2062
URL: https://issues.apache.org/jira/browse/KAFKA-2062
+1
On Fri, Mar 27, 2015 at 01:34:54PM -0700, Neha Narkhede wrote:
+1
Thanks Becket!
On Fri, Mar 27, 2015 at 1:19 PM, Jay Kreps jay.kr...@gmail.com wrote:
+1
Thanks for your patience Jiangjie!
-Jay
On Fri, Mar 27, 2015 at 11:48 AM, Jiangjie Qin j...@linkedin.com.invalid
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384654#comment-14384654
]
Joel Koshy commented on KAFKA-1546:
---
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384660#comment-14384660
]
Rajiv Kurian edited comment on KAFKA-2045 at 3/27/15 9:07 PM:
--
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384610#comment-14384610
]
Joel Koshy commented on KAFKA-1546:
---
Actually, I'm referring to the documentation html -
[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384660#comment-14384660
]
Rajiv Kurian commented on KAFKA-2045:
-
1. We can actually make serious performance
+1 (non-binding)
I really like the new API.
One thing to clarify in the docs:
If sender thread calls close(), it will block forever. So if a
close() call is called from sender thread, an error message will be
put in the log and close(0) will be called instead.
I think we should explicitly
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Auradkar updated KAFKA-1546:
---
Attachment: documentation.diff
Automate replica lag tuning
---
[
https://issues.apache.org/jira/browse/KAFKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384762#comment-14384762
]
David Chu commented on KAFKA-1716:
--
[~becket_qin] I was able to reproduce the same issue
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31366/
---
(Updated March 27, 2015, 10:31 p.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384810#comment-14384810
]
Sriharsha Chintalapani commented on KAFKA-1461:
---
Updated reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384813#comment-14384813
]
Sriharsha Chintalapani commented on KAFKA-1461:
---
[~guozhang] addressed your
[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated KAFKA-1461:
--
Attachment: KAFKA-1461_2015-03-27_15:31:11.patch
Replica fetcher thread does
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31366/#review78120
---
Couple of comments. Thanks!
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Auradkar updated KAFKA-1546:
---
Status: Patch Available (was: Open)
Automate replica lag tuning
[
https://issues.apache.org/jira/browse/KAFKA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384759#comment-14384759
]
Aditya Auradkar commented on KAFKA-1546:
Added a patch for the HTML changes.
[
https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1809:
Attachment: KAFKA-1809_2015-03-27_15:04:10.patch
Refactor brokers to allow listening on multiple
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28769/
---
(Updated March 27, 2015, 10:04 p.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384769#comment-14384769
]
Gwen Shapira commented on KAFKA-1809:
-
Updated reviewboard
Thanks everyone for the patient discussion. I really learned a lot from it!
KIP-15 is closed with 3 binding +1 and 1 non-binding +1.
(Will improve the KIP description as Gwen suggested.)
On 3/27/15, 2:05 PM, Gwen Shapira gshap...@cloudera.com wrote:
+1 (non-binding)
I really like the new API.
[
https://issues.apache.org/jira/browse/KAFKA-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384782#comment-14384782
]
Gwen Shapira commented on KAFKA-1809:
-
[~junrao] - the latest patch is:
[
https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384895#comment-14384895
]
Jiangjie Qin commented on KAFKA-1660:
-
Updated reviewboard
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31850/
---
(Updated March 27, 2015, 11:35 p.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiangjie Qin updated KAFKA-1660:
Attachment: KAFKA-1660_2015-03-27_16:35:42.patch
Ability to call close() with a timeout on the
On March 27, 2015, 10:52 p.m., Aditya Auradkar wrote:
core/src/main/scala/kafka/server/AbstractFetcherThread.scala, line 276
https://reviews.apache.org/r/31366/diff/3/?file=908482#file908482line276
Can you add some documentation for this class?
Thanks for the review. Updated the
[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384922#comment-14384922
]
Sriharsha Chintalapani commented on KAFKA-1461:
---
Updated reviewboard
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31366/
---
(Updated March 27, 2015, 11:56 p.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated KAFKA-1461:
--
Attachment: KAFKA-1461_2015-03-27_16:56:45.patch
Replica fetcher thread does
For the samples: it will be at least double that estimate I think
since the long array contains (eight byte) references to the actual
longs, each of which also have some object overhead.
Re: testing: actually, it looks like YM metrics does allow you to
drop in your own clock:
Just sent out an invite for Mar 31 at 11am PST. The following is the
tentative agenda. Let me know if you want to attend, but haven't received
an invite.
Agenda:
KIP-4 (admin commands):
* wrap up any remaining issues
KIP-13 (quota):
* dependency on using the new metrics package
* dependency
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31366/
---
(Updated March 28, 2015, 12:02 a.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384932#comment-14384932
]
Sriharsha Chintalapani commented on KAFKA-1461:
---
Updated reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated KAFKA-1461:
--
Attachment: KAFKA-1461_2015-03-27_17:02:32.patch
Replica fetcher thread does
I think we decided that we should reconvene next Tuesday to collect
everyone's thoughts on metrics and discuss other KIPs. Can everyone
still do Tuesday or do people feel we need to push that further out by
a few days?
Thanks,
Joel
On Tue, Mar 24, 2015 at 12:28:04PM -0700, Jun Rao wrote:
Just
A few more comments.
Currently, we control the YM jmx metric name by using a different
constructor of MetricName. So, the jmx names should remain unchanged when
upgrading YM. We probably should check if that constructor still exists in
the new version of YM.
The current histogram implementation
65 matches
Mail list logo
