RE: [VOTE] KIP-21 Dynamic Configuration

Minor edit: I meant that we should expect change notifications in the old format made earlier, but should perhaps ignore them. After the upgrade is done, older versions of AdminTools can no longer be used to make config changes. Aditya From: Aditya Aurad

Re: Nagging - pending review requests :)

see below On Fri, May 29, 2015 at 2:25 AM, Jaikiran Pai wrote: > Could someone please look at these few review requests and let me know if > any changes are needed: > > https://reviews.apache.org/r/34394/ related to > https://issues.apache.org/jira/browse/KAFKA-1907 I haven't looked at all the

[jira] [Updated] (KAFKA-2223) Improve distribution of data when using hash-based partitioning

[ https://issues.apache.org/jira/browse/KAFKA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Reid updated KAFKA-2223: Resolution: Won't Fix Status: Resolved (was: Patch Available) Closing as Won't Fix because

Nagging - pending review requests :)

Could someone please look at these few review requests and let me know if any changes are needed: https://reviews.apache.org/r/34394/ related to https://issues.apache.org/jira/browse/KAFKA-1907 https://reviews.apache.org/r/30403/ related to https://issues.apache.org/jira/browse/KAFKA-1906 Th

RE: [VOTE] KIP-21 Dynamic Configuration

Yeah, the same cleaning mechanism will be carried over. > 1. Are we introducing a new Java API for the config change protocol and if > so where will that appear? Is that going to be part of the java api in the > admin api kip? Let's document that. Yeah, we need to introduce a new Java API for the

RE: [DISCUSS] KIP-4 - Command line and centralized administrative operations (Thread 2)

Thanks. Perhaps we should leave TMR unchanged for now. Should we discuss this during the next hangout? Aditya From: Jun Rao [j...@confluent.io] Sent: Thursday, May 28, 2015 5:32 PM To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-4 - Command line and c

[jira] [Commented] (KAFKA-2225) Allow fetching from ISR

[ https://issues.apache.org/jira/browse/KAFKA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564226#comment-14564226 ] Theo Hultberg commented on KAFKA-2225: -- Yes, we use the private IP. > Allow fetching

Re: [DISCUSSION] Can we move the ack timeout in ProducerRequest to broker?

Jun, Jay and Joel, thanks a lot for the explanations. Just summarize what I learned - please correct me if I understand wrong: 1. The actually replication time is determined by inter-broker (intra-cluster) communication. 2. The actual replication time for different topics may be different. 3. The

Re: Review Request 34734: Patch for KAFKA-2226

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34734/#review85665 --- Thanks for the new patch. A few more clarification questions below.

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564029#comment-14564029 ] Jun Rao commented on KAFKA-1367: Well, in that approach, you still have the problem on the

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564012#comment-14564012 ] Joel Koshy commented on KAFKA-1367: --- One minor issue with depending on the TMR for KAKFA

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564002#comment-14564002 ] Jun Rao commented on KAFKA-1367: It's probably better to always let the controller propaga

Re: [DISCUSS] KIP-4 - Command line and centralized administrative operations (Thread 2)

There is a reasonable use case of ISR in KAFKA-2225. Basically, for economical reasons, we may want to let a consumer fetch from a replica in ISR that's in the same zone. In order to support that, it will be convenient to have TMR return the correct ISR for the consumer to choose. So, perhaps it's

Re: [VOTE] KIP-21 Dynamic Configuration

That is handled now so I am assuming the same mechanism carries over? -Jay On Thu, May 28, 2015 at 5:12 PM, Guozhang Wang wrote: > For the sequential config/changes/config_change_XX znode, do we have any > manners to do cleaning in order to avoid the change-log from growing > indefinitely? > >

[jira] [Updated] (KAFKA-2185) Update to Gradle 2.4

[ https://issues.apache.org/jira/browse/KAFKA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2185: --- Resolution: Fixed Fix Version/s: 0.8.3 Status: Resolved (was: Patch Available) Thanks for t

[jira] [Commented] (KAFKA-2168) New consumer poll() can block other calls like position(), commit(), and close() indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563968#comment-14563968 ] Jason Gustafson commented on KAFKA-2168: This patch is a work in progress. Using t

[jira] [Commented] (KAFKA-2226) NullPointerException in TestPurgatoryPerformance

[ https://issues.apache.org/jira/browse/KAFKA-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563965#comment-14563965 ] Yasuhiro Matsuda commented on KAFKA-2226: - Updated reviewboard https://reviews.apa

Re: Review Request 34734: Patch for KAFKA-2226

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34734/ --- (Updated May 29, 2015, 12:19 a.m.) Review request for kafka. Bugs: KAFKA-2226

[jira] [Updated] (KAFKA-2226) NullPointerException in TestPurgatoryPerformance

[ https://issues.apache.org/jira/browse/KAFKA-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasuhiro Matsuda updated KAFKA-2226: Attachment: KAFKA-2226_2015-05-28_17:18:55.patch > NullPointerException in TestPurgatoryPerf

[jira] [Created] (KAFKA-2230) Add a wakeup() call to the new consumer

Jay Kreps created KAFKA-2230: Summary: Add a wakeup() call to the new consumer Key: KAFKA-2230 URL: https://issues.apache.org/jira/browse/KAFKA-2230 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563960#comment-14563960 ] Joel Koshy commented on KAFKA-1367: --- Jun - that is a good point. That sounds like a good

Re: [VOTE] KIP-21 Dynamic Configuration

For the sequential config/changes/config_change_XX znode, do we have any manners to do cleaning in order to avoid the change-log from growing indefinitely? Guozhang On Thu, May 28, 2015 at 5:02 PM, Jay Kreps wrote: > I still have a couple of questions: > 1. Are we introducing a new Java API for

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 7:10 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/utils/timer/TimerTaskList.scala, lines 132-135 > > > > > > So, I guess the race condition is the following. The expiration thread > > moves a

Re: [VOTE] KIP-21 Dynamic Configuration

I still have a couple of questions: 1. Are we introducing a new Java API for the config change protocol and if so where will that appear? Is that going to be part of the java api in the admin api kip? Let's document that. 2. The proposed JSON format uses camel case for field names, is that what we'

Re: [VOTE] KIP-21 Dynamic Configuration

I still have a couple of questions: 1. Are we introducing a new Java API for the config change protocol and if so where will that appear? Is that going to be part of the java api in the admin api kip? Let's document that. 2. The proposed JSON format uses camel case for field names, is that what we'

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563935#comment-14563935 ] Jun Rao commented on KAFKA-1367: There is actually a reasonable use case of ISR in KAFKA-2

Re: [DISCUSSION] Can we move the ack timeout in ProducerRequest to broker?

The purpose of the replication timeout was not to control the purgatory size but rather to bound the time you block on replication to other servers. We discussed making it a server-side config but the rationale for making a client configuration is that these timeouts are fundamentally about how lo

Re: Review Request 34789: Patch for KAFKA-2168

> On May 28, 2015, 11:30 p.m., Ewen Cheslack-Postava wrote: > > clients/src/main/java/org/apache/kafka/clients/consumer/KafkaConsumer.java, > > line 857 > > > > > > I think this requires a bit more coordination betwee

Re: Review Request 34524: Fix KAFKA-2208

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34524/#review85641 --- clients/src/main/java/org/apache/kafka/clients/consumer/internals/C

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563904#comment-14563904 ] Ashish K Singh commented on KAFKA-1367: --- Thanks [~jjkoshy]! I will update the KIP ac

Re: Review Request 34789: Patch for KAFKA-2168

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34789/#review85644 --- I think close() isn't quite right, and is probably harder than just

[jira] [Resolved] (KAFKA-948) ISR list in LeaderAndISR path not updated for partitions when Broker (which is not leader) is down

[ https://issues.apache.org/jira/browse/KAFKA-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-948. --- Resolution: Cannot Reproduce Closing this since it's no longer active. > ISR list in LeaderAndISR path not upd

Re: [DISCUSSION] Can we move the ack timeout in ProducerRequest to broker?

> have a Kafka cluster across availability zones, data will be replicated to ... > single timeout on the broker side. In theory, different producers may want > to pick different replication time depending on the topics being sent. I think Becket raises a good point here in that the above configura

Re: [VOTE] KIP-21 Dynamic Configuration

+1. Thanks, Jun On Thu, May 28, 2015 at 11:41 AM, Aditya Auradkar < aaurad...@linkedin.com.invalid> wrote: > bump > > > From: Aditya Auradkar > Sent: Tuesday, May 26, 2015 1:16 PM > To: dev@kafka.apache.org > Subject: RE: [VOTE] KIP-21 Dynamic Configurat

Re: [DISCUSSION] Can we move the ack timeout in ProducerRequest to broker?

Hi, Jiangjie, The replication time may vary a bit for different partitions. For example, a partition with more replicas may take a bit more time to propagate the messages. Also, the replication time depends on network latency. If you have a Kafka cluster across availability zones, data will be rep

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563858#comment-14563858 ] Joel Koshy commented on KAFKA-1367: --- Hi [~singhashish] - sorry I missed your pings. Yes

[jira] [Commented] (KAFKA-2168) New consumer poll() can block other calls like position(), commit(), and close() indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563843#comment-14563843 ] Jason Gustafson commented on KAFKA-2168: I've added a patch which removes synchron

[jira] [Commented] (KAFKA-2168) New consumer poll() can block other calls like position(), commit(), and close() indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563832#comment-14563832 ] Jason Gustafson commented on KAFKA-2168: Created reviewboard https://reviews.apach

[jira] [Updated] (KAFKA-2168) New consumer poll() can block other calls like position(), commit(), and close() indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2168: --- Attachment: KAFKA-2168.patch > New consumer poll() can block other calls like position(), comm

[jira] [Updated] (KAFKA-2168) New consumer poll() can block other calls like position(), commit(), and close() indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2168: --- Status: Patch Available (was: Open) > New consumer poll() can block other calls like position

Review Request 34789: Patch for KAFKA-2168

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34789/ --- Review request for kafka. Bugs: KAFKA-2168 https://issues.apache.org/jira/b

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 7:10 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/utils/timer/TimerTaskList.scala, lines 132-135 > > > > > > So, I guess the race condition is the following. The expiration thread > > moves a

[jira] [Commented] (KAFKA-1367) Broker topic metadata not kept in sync with ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563795#comment-14563795 ] Ashish K Singh commented on KAFKA-1367: --- [~jjkoshy] pinging you for your confirmatio

[jira] [Commented] (KAFKA-2168) New consumer poll() can block other calls like position(), commit(), and close() indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563753#comment-14563753 ] Guozhang Wang commented on KAFKA-2168: -- I would also prefer to stick with single-thre

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 7:10 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/utils/timer/TimerTaskList.scala, lines 132-135 > > > > > > So, I guess the race condition is the following. The expiration thread > > moves a

[jira] [Commented] (KAFKA-2225) Allow fetching from ISR

[ https://issues.apache.org/jira/browse/KAFKA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563732#comment-14563732 ] Jun Rao commented on KAFKA-2225: [~iconara], just to clarify, so you are using the private

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 7:10 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/utils/timer/TimerTaskList.scala, lines 132-135 > > > > > > So, I guess the race condition is the following. The expiration thread > > moves a

[jira] [Updated] (KAFKA-2186) Follow-up patch of KAFKA-1650

[ https://issues.apache.org/jira/browse/KAFKA-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2186: -- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch - committed to t

[jira] [Updated] (KAFKA-2091) Expose a Partitioner interface in the new producer

[ https://issues.apache.org/jira/browse/KAFKA-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2091: -- Thanks for the patch - committed to trunk. > Expose a Partitioner interface in the new producer > -

[jira] [Resolved] (KAFKA-2224) kafka-consumer-offset-checker when kafka offset storage is used

[ https://issues.apache.org/jira/browse/KAFKA-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-2224. - Resolution: Duplicate Duplicate of KAFKA-1951 > kafka-consumer-offset-checker when kafka offset s

[jira] [Commented] (KAFKA-2224) kafka-consumer-offset-checker when kafka offset storage is used

[ https://issues.apache.org/jira/browse/KAFKA-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563652#comment-14563652 ] Jiangjie Qin commented on KAFKA-2224: - Seems to be duplicate of KAFKA-1951. > kafka-c

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 7:10 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/utils/timer/TimerTaskList.scala, lines 132-135 > > > > > > So, I guess the race condition is the following. The expiration thread > > moves a

Re: Review Request 32869: Patch for KAFKA-2091

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/32869/#review85608 --- Ship it! Ship It! - Joel Koshy On May 27, 2015, 10:50 p.m., Srih

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 7:10 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/utils/timer/TimerTaskList.scala, lines 132-135 > > > > > > So, I guess the race condition is the following. The expiration thread > > moves a

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 7:10 p.m., Jun Rao wrote: > > Thanks for the patch. A couple of questions below. > > > > Also, in TimerTask.setTimerTaskEntry(), the comment suggests that the > > TaskEntry can change for a TimerTask. However, it seems that we set the > > entry for the task only during entry

Re: Review Request 34734: Patch for KAFKA-2226

> On May 28, 2015, 8:42 a.m., Onur Karaman wrote: > > It seems like you're concerned about adding/removing a TimerTaskEntry that > > already exists in another TimerTaskList. Can you explain how that can > > happen? My understanding of the timing wheel stuff is only so-so. For adding, a TimerTa

Re: Review Request 34734: Patch for KAFKA-2226

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34734/#review85596 --- Thanks for the patch. A couple of questions below. Also, in TimerTa

Re: [VOTE] KIP-21 Dynamic Configuration

+1 (non binding) > On May 28, 2015, at 11:41 AM, Aditya Auradkar > wrote: > > bump > > > From: Aditya Auradkar > Sent: Tuesday, May 26, 2015 1:16 PM > To: dev@kafka.apache.org > Subject: RE: [VOTE] KIP-21 Dynamic Configuration > > Hey everyone, > > Co

RE: [VOTE] KIP-21 Dynamic Configuration

bump From: Aditya Auradkar Sent: Tuesday, May 26, 2015 1:16 PM To: dev@kafka.apache.org Subject: RE: [VOTE] KIP-21 Dynamic Configuration Hey everyone, Completed the changes to KIP-4. After today's hangout, there doesn't appear to be anything remaining to

[jira] [Updated] (KAFKA-2189) Snappy compression of message batches less efficient in 0.8.2.1

[ https://issues.apache.org/jira/browse/KAFKA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2189: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch. +1 and committed to t

[jira] [Commented] (KAFKA-2168) New consumer poll() can block other calls like position(), commit(), and close() indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563212#comment-14563212 ] Jason Gustafson commented on KAFKA-2168: Talked with Neha, Ewen, and Jay last nigh

Re: Mesos Community Networking Hangout

sorry, wrong email list :) ~ Joe Stein - - - - - - - - - - - - - - - - - http://www.stealth.ly - - - - - - - - - - - - - - - - - On Thu, May 28, 2015 at 11:41 AM, Joe Stein wrote: > Hi, a few folks from a few different companies (Cisco, Elodina, > Mesosphere, Moz) are going to be having a h

Re: Review Request 33049: Patch for KAFKA-2084

> On May 28, 2015, 12:58 p.m., Manikumar Reddy O wrote: > > core/src/main/scala/kafka/server/ClientQuotaMetrics.scala, line 145 > > > > > > Are we using clientID as uniqueKey?. But as of now, clientID is not > > mand

Mesos Community Networking Hangout

Hi, a few folks from a few different companies (Cisco, Elodina, Mesosphere, Moz) are going to be having a hangout https://plus.google.com/hangouts/_/stealth.ly/mesos-network every Friday 11am PT / 2pm ET and wanted to invite any other interested parties to join too. We have already talked with fol

[jira] [Commented] (KAFKA-2223) Improve distribution of data when using hash-based partitioning

[ https://issues.apache.org/jira/browse/KAFKA-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563030#comment-14563030 ] Gabriel Reid commented on KAFKA-2223: - Ok, thanks for taking a look [~jkreps]. I had

[jira] [Updated] (KAFKA-2229) Phase 1: Requests and KafkaApis

[ https://issues.apache.org/jira/browse/KAFKA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Biletskyi updated KAFKA-2229: Status: Patch Available (was: Open) > Phase 1: Requests and KafkaApis > ---

[jira] [Commented] (KAFKA-2229) Phase 1: Requests and KafkaApis

[ https://issues.apache.org/jira/browse/KAFKA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562877#comment-14562877 ] Andrii Biletskyi commented on KAFKA-2229: - Created reviewboard https://reviews.apa

Review Request 34766: Patch for KAFKA-2229

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34766/ --- Review request for kafka. Bugs: KAFKA-2229 https://issues.apache.org/jira/b

[jira] [Updated] (KAFKA-2229) Phase 1: Requests and KafkaApis

[ https://issues.apache.org/jira/browse/KAFKA-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Biletskyi updated KAFKA-2229: Attachment: KAFKA-2229.patch > Phase 1: Requests and KafkaApis > ---

[jira] [Created] (KAFKA-2229) Phase 1: Requests and KafkaApis

Andrii Biletskyi created KAFKA-2229: --- Summary: Phase 1: Requests and KafkaApis Key: KAFKA-2229 URL: https://issues.apache.org/jira/browse/KAFKA-2229 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-2228) Phase 1: Requests and KafkaApis

Andrii Biletskyi created KAFKA-2228: --- Summary: Phase 1: Requests and KafkaApis Key: KAFKA-2228 URL: https://issues.apache.org/jira/browse/KAFKA-2228 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-2227) Phase 1: Requests and KafkaApis

Andrii Biletskyi created KAFKA-2227: --- Summary: Phase 1: Requests and KafkaApis Key: KAFKA-2227 URL: https://issues.apache.org/jira/browse/KAFKA-2227 Project: Kafka Issue Type: Sub-task

Re: Review Request 33049: Patch for KAFKA-2084

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33049/#review85545 --- core/src/main/scala/kafka/server/ClientQuotaMetrics.scala

Re: Review Request 34734: Patch for KAFKA-2226

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34734/#review85530 --- It seems like you're concerned about adding/removing a TimerTaskEntr

[jira] [Commented] (KAFKA-2187) Introduce merge-kafka-pr.py script

[ https://issues.apache.org/jira/browse/KAFKA-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562478#comment-14562478 ] Ismael Juma commented on KAFKA-2187: [~nehanarkhede], please let me know if there's an

[jira] [Commented] (KAFKA-2185) Update to Gradle 2.4

[ https://issues.apache.org/jira/browse/KAFKA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562472#comment-14562472 ] Ismael Juma commented on KAFKA-2185: Anything I can do to help move this along? People

[jira] [Commented] (KAFKA-2189) Snappy compression of message batches less efficient in 0.8.2.1

[ https://issues.apache.org/jira/browse/KAFKA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562470#comment-14562470 ] Ismael Juma commented on KAFKA-2189: Given the positive feedback, it seems like it wou