[jira] [Commented] (KAFKA-2122) Remove controller.message.queue.size Config

[ https://issues.apache.org/jira/browse/KAFKA-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502583#comment-14502583 ] 王博 commented on KAFKA-2122: --- Which version this patch is based on? I found KAFKA-2122_2015-04-1

[jira] [Comment Edited] (KAFKA-2122) Remove controller.message.queue.size Config

[ https://issues.apache.org/jira/browse/KAFKA-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502583#comment-14502583 ] Bo Wang edited comment on KAFKA-2122 at 4/20/15 10:27 AM: -- Which

[jira] [Created] (KAFKA-2134) Producer blocked on metric publish

Vamsi Subhash Achanta created KAFKA-2134: Summary: Producer blocked on metric publish Key: KAFKA-2134 URL: https://issues.apache.org/jira/browse/KAFKA-2134 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-2134) Producer blocked on metric publish

[ https://issues.apache.org/jira/browse/KAFKA-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsi Subhash Achanta updated KAFKA-2134: - Description: Hi, We have a REST api to publish to a topic. Yesterday, we started

[jira] [Commented] (KAFKA-2122) Remove controller.message.queue.size Config

[ https://issues.apache.org/jira/browse/KAFKA-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502761#comment-14502761 ] Sriharsha Chintalapani commented on KAFKA-2122: --- [~wangbo23] This is for tru

Re: [jira] [Commented] (KAFKA-2122) Remove controller.message.queue.size Config

unsubscribe > On Apr 20, 2015, at 8:09 AM, Sriharsha Chintalapani (JIRA) > wrote: > > >[ > https://issues.apache.org/jira/browse/KAFKA-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502761#comment-14502761 > ] > > Sriharsha Chintalapani com

[jira] [Commented] (KAFKA-2055) ConsumerBounceTest.testSeekAndCommitWithBrokerFailures transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503051#comment-14503051 ] Fangmin Lv commented on KAFKA-2055: --- There is a case that the leader is shutting down ju

Re: Review Request 33242: Patch for KAFKA-2121

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33242/ --- (Updated April 20, 2015, 4:06 p.m.) Review request for kafka. Bugs: KAFKA-212

[jira] [Updated] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Zhen Wu updated KAFKA-2121: -- Attachment: KAFKA-2121_2015-04-20_09:06:09.patch > prevent potential resource leak in KafkaProdu

[jira] [Commented] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503086#comment-14503086 ] Steven Zhen Wu commented on KAFKA-2121: --- Updated reviewboard https://reviews.apache.

Re: Review Request 32781: Patch for KAFKA-2087

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/32781/#review80733 --- Ship it! Ship It! - Neha Narkhede On April 2, 2015, 5:29 p.m., A

[jira] [Commented] (KAFKA-2118) Cleaner cannot clean after shutdown during replaceSegments

[ https://issues.apache.org/jira/browse/KAFKA-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503128#comment-14503128 ] Jay Kreps commented on KAFKA-2118: -- I don't think I'll get to it, go ahead without me. Ju

[jira] [Updated] (KAFKA-2087) TopicConfigManager javadoc references incorrect paths

[ https://issues.apache.org/jira/browse/KAFKA-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-2087: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. Thanks! > Top

[jira] [Updated] (KAFKA-2087) TopicConfigManager javadoc references incorrect paths

[ https://issues.apache.org/jira/browse/KAFKA-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-2087: - Reviewer: Neha Narkhede > TopicConfigManager javadoc references incorrect paths >

Re: Review Request 32869: Patch for KAFKA-2091

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/32869/#review80738 --- clients/src/main/java/org/apache/kafka/clients/producer/Partitioner

[jira] [Commented] (KAFKA-873) Consider replacing zkclient with curator (with zkclient-bridge)

[ https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503169#comment-14503169 ] Neha Narkhede commented on KAFKA-873: - I'm not so sure yet that moving to Curator is a

[jira] [Updated] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Zhen Wu updated KAFKA-2121: -- Attachment: KAFKA-2121_2015-04-20_09:51:51.patch > prevent potential resource leak in KafkaProdu

Re: Review Request 33242: Patch for KAFKA-2121

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33242/ --- (Updated April 20, 2015, 4:51 p.m.) Review request for kafka. Bugs: KAFKA-212

[jira] [Commented] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503172#comment-14503172 ] Steven Zhen Wu commented on KAFKA-2121: --- Updated reviewboard https://reviews.apache.

Re: Review Request 33242: Patch for KAFKA-2121

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33242/ --- (Updated April 20, 2015, 4:52 p.m.) Review request for kafka. Bugs: KAFKA-212

[jira] [Updated] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Zhen Wu updated KAFKA-2121: -- Attachment: KAFKA-2121_2015-04-20_09:52:46.patch > prevent potential resource leak in KafkaProdu

[jira] [Commented] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503176#comment-14503176 ] Steven Zhen Wu commented on KAFKA-2121: --- Updated reviewboard https://reviews.apache.

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14503174#comment-14503174 ] Jay Kreps commented on KAFKA-2091: -- This is waiting on the KIP which would be the best pl

[jira] [Commented] (KAFKA-873) Consider replacing zkclient with curator (with zkclient-bridge)

[ https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503179#comment-14503179 ] Jordan Zimmerman commented on KAFKA-873: [~nehanarkhede] - the major upside with Cu

Re: Review Request 33027: Fix timing issue in DelayedOperationTest

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33027/#review80742 --- Ship it! Ship It! - Neha Narkhede On April 9, 2015, 6:04 p.m., R

[jira] [Updated] (KAFKA-2057) DelayedOperationTest.testRequestExpiry transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-2057: - Resolution: Fixed Reviewer: Neha Narkhede Status: Resolved (was: Patch Available) T

[jira] [Updated] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Zhen Wu updated KAFKA-2121: -- Attachment: KAFKA-2121_2015-04-20_09:57:49.patch > prevent potential resource leak in KafkaProdu

[jira] [Commented] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503190#comment-14503190 ] Steven Zhen Wu commented on KAFKA-2121: --- Updated reviewboard https://reviews.apache.

Re: Review Request 33242: Patch for KAFKA-2121

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33242/ --- (Updated April 20, 2015, 4:57 p.m.) Review request for kafka. Bugs: KAFKA-212

Build failed in Jenkins: KafkaPreCommit #81

See Changes: [neha.narkhede] TopicConfigManager javadoc references incorrect paths; reviewed by Neha Narkhede -- [...truncated 1557 lines...] kafka.api.ProducerFailureHandlingTest > testInvalidPart

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14503197#comment-14503197 ] Sriharsha Chintalapani commented on KAFKA-2091: --- [~jkreps] Thanks for the re

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Hi Parth, Nice work on this KIP. I did another read through and had a few more comments (with edits after I went through the thread). Many of these comments were brought up by others as well, so it appears that the KIP would benefit from an update at this point to incorporate comments from the th

[jira] [Commented] (KAFKA-2035) Add a topic config cache.

[ https://issues.apache.org/jira/browse/KAFKA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503222#comment-14503222 ] Jay Kreps commented on KAFKA-2035: -- Hey [~parth.brahmbhatt] I'm not picky about the seque

Jenkins build is back to normal : Kafka-trunk #470

See

Re: Review Request 31850: Patch for KAFKA-1660

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/31850/#review80753 --- clients/src/main/java/org/apache/kafka/clients/producer/KafkaProduc

[jira] [Commented] (KAFKA-1646) Improve consumer read performance for Windows

[ https://issues.apache.org/jira/browse/KAFKA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503261#comment-14503261 ] Jay Kreps commented on KAFKA-1646: -- Cool, this looks good to me. This introduces a new co

[jira] [Commented] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503279#comment-14503279 ] Steven Zhen Wu commented on KAFKA-2121: --- [~ewencp] I made two more changes in latest

[jira] [Commented] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503278#comment-14503278 ] Steven Zhen Wu commented on KAFKA-2121: --- [~ewencp] I made two more changes in latest

Re: [DISCUSS] KIP-12 - Kafka Sasl/Kerberos implementation

Hi,      I updated the KIP-12 with more details. Please take a look   https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=51809888 Thanks, Harsha On February 11, 2015 at 10:02:43 AM, Harsha (ka...@harsha.io) wrote: Thanks Joe. It will be part of KafkaServer and will run on its own

[jira] [Commented] (KAFKA-2035) Add a topic config cache.

[ https://issues.apache.org/jira/browse/KAFKA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503297#comment-14503297 ] Parth Brahmbhatt commented on KAFKA-2035: - [~jkreps] yes that is the difference I

[jira] [Created] (KAFKA-2135) New Kafka Producer Client: Send requests wait indefinitely if no broker is available.

David Hay created KAFKA-2135: Summary: New Kafka Producer Client: Send requests wait indefinitely if no broker is available. Key: KAFKA-2135 URL: https://issues.apache.org/jira/browse/KAFKA-2135 Project:

Re: Review Request 33065: Patch for KAFKA-1928

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33065/#review80761 --- clients/src/main/java/org/apache/kafka/common/network/NetworkReceiv

Re: Review Request 33242: Patch for KAFKA-2121

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33242/#review80770 --- Ship it! New version with KafkaConsumer changes looks good, passes

Build failed in Jenkins: KafkaPreCommit #82

See Changes: [neha.narkhede] DelayedOperationTest.testRequestExpiry transient failure; reviewed by Neha Narkhede -- [...truncated 659 lines...] kafka.api.ProducerFailureHandlingTest > testInvalidPa

[jira] [Updated] (KAFKA-2126) New consumer does not correctly configure deserializers

[ https://issues.apache.org/jira/browse/KAFKA-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-2126: - Resolution: Duplicate Status: Resolved (was: Patch Available) KAFKA-2121

[jira] [Commented] (KAFKA-2121) prevent potential resource leak in KafkaProducer and KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503345#comment-14503345 ] Ewen Cheslack-Postava commented on KAFKA-2121: -- Latest patch LGTM, maybe [~ju

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Hi Joel, Thanks for the review and I plan to update the KIP today with all the updated info. My comments in line below. Thanks Parth On 4/20/15, 10:07 AM, "Joel Koshy" mailto:jjkosh...@gmail.com>> wrote: Hi Parth, Nice work on this KIP. I did another read through and had a few more commen

[jira] [Commented] (KAFKA-2024) Cleaner can generate unindexable log segments

[ https://issues.apache.org/jira/browse/KAFKA-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503401#comment-14503401 ] Mayuresh Gharat commented on KAFKA-2024: Shouldn't the offsetIndex.scala should ha

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Just a followup question. Suppose there are two rules. Rule1 allows user1 and rule2 denies user2. Does user3 have access? If not, does removing rule1 enable user3 access? Thanks, Jun On Mon, Apr 20, 2015 at 1:34 PM, Parth Brahmbhatt < pbrahmbh...@hortonworks.com> wrote: > > Hi Joel, > > Thanks

Re: [DISCUSS] KIP-12 - Kafka Sasl/Kerberos implementation

Hi, Harsha, For SASL, a common use case is the integration with LDAP/AD. For completeness, could you describe (or provide a link) how such integration can be done? Also, what about the SSL support, do you plan to describe it in same same KIP or a separate one? Thanks, Jun On Mon, Apr 20, 2015

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

1. Yes, lag is probably only going to be useful for the admin client. However, so is isr. It seems to me that we should get lag and isr from the same request. I was thinking that we can just extend TMR by changing replicas from an array of int to an array of (int, lag) pairs. Is that too complicate

[jira] [Commented] (KAFKA-873) Consider replacing zkclient with curator (with zkclient-bridge)

[ https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503528#comment-14503528 ] Aaron Dixon commented on KAFKA-873: --- In addition, Curator supports discovery of zookeeper

Re: [DISCUSS] KIP-19 Add a request timeout to NetworkClient

Jiangjie, Allowing messages to be accumulated in an offline partition could be useful since the partition may become available before the request timeout or linger time is reached. Now that we are planning to add a new timeout, it would be useful to think through whether/how that applies to messag

Re: [DISCUSS] KIP-11- Authorization design for kafka security

user3 does not have access and removing the deny rule does not grant him or user2 access. user2 even without the deny rule will not have access. Thanks Parth On 4/20/15, 12:03 PM, "Jun Rao" wrote: >Just a followup question. Suppose there are two rules. Rule1 allows user1 >and rule2 denies user2

Re: [DISCUSS] KIP-12 - Kafka Sasl/Kerberos implementation

Hi Jun,            I am using the underlying protocol GSS-API that sasl also uses. I can add details about LDAP/AD . For AD , this is in general the integration of AD to KERBEROS. I.e   kerberos can talk to AD to get the kinit login credentials ( more of a setup details between kerberos and AD)

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Hmm, I thought the semantics is that if you only have rule "deny user2", it means that everyone except user2 has access? Thanks, Jun On Mon, Apr 20, 2015 at 3:25 PM, Parth Brahmbhatt < pbrahmbh...@hortonworks.com> wrote: > user3 does not have access and removing the deny rule does not grant him

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Hi Parth, OK, I understand your approach much better, now. I don’t really have a strong opinion; I guess I just shared Gwen’s concern (in the hangout) that, with this approach, if a site implements their own authorizer using their own ACL implementation, it will work, but they’ll have this vestigi

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Ignore my last; I was catching up on this list & hadn’t seen Gwen’s subsequent proposal. On 4/15/15, 5:15 PM, "Parth Brahmbhatt" wrote: >Kafka currently stores logConfig overrides specified during topic creation >in zookeeper, its just an instance of java.util.Properties converted to >json. I am

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Here is a pseudo code that explains my current approach: acls = authorizer.getAcl(resource) if(acls == null || acls.isEmpty) { allow all requests for backward compatibility. (any topics that were created prior to security support will not have acls) This is debatable , generally we should

[jira] [Updated] (KAFKA-1646) Improve consumer read performance for Windows

[ https://issues.apache.org/jira/browse/KAFKA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1646: - Status: In Progress (was: Patch Available) > Improve consumer read performance for Windows >

[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 ] Jay Kreps updated KAFKA-2091: - Status: In Progress (was: Patch Available) > Expose a Partitioner interface in the new producer > ---

[jira] [Updated] (KAFKA-1660) Ability to call close() with a timeout on the Java Kafka Producer.

[ https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1660: - Status: In Progress (was: Patch Available) > Ability to call close() with a timeout on the Java Kafka Pro

[jira] [Updated] (KAFKA-1933) Fine-grained locking in log append

[ https://issues.apache.org/jira/browse/KAFKA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1933: - Status: In Progress (was: Patch Available) These results are very good. I'm scared of the code. The chang

[jira] [Updated] (KAFKA-2035) Add a topic config cache.

[ https://issues.apache.org/jira/browse/KAFKA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-2035: - Status: In Progress (was: Patch Available) [~parth.brahmbhatt] Unless you object I'd prefer to either fig

[jira] [Commented] (KAFKA-2035) Add a topic config cache.

[ https://issues.apache.org/jira/browse/KAFKA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503888#comment-14503888 ] Parth Brahmbhatt commented on KAFKA-2035: - Makes sense. I will close this jira and

[jira] [Created] (KAFKA-2136) Client side protocol changes to return quota delays

Aditya Auradkar created KAFKA-2136: -- Summary: Client side protocol changes to return quota delays Key: KAFKA-2136 URL: https://issues.apache.org/jira/browse/KAFKA-2136 Project: Kafka Issue T

[jira] [Updated] (KAFKA-2136) Client side protocol changes to return quota delays

[ https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Auradkar updated KAFKA-2136: --- Reviewer: Joel Koshy > Client side protocol changes to return quota delays > -

[jira] [Updated] (KAFKA-2000) Delete consumer offsets from kafka once the topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2000: -- Status: In Progress (was: Patch Available) > Delete consumer offsets from kafka once the topic is delet

Re: Review Request 32650: Patch for KAFKA-2000

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

Review Request 33378: Patch for KAFKA-2136

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

[jira] [Commented] (KAFKA-2136) Client side protocol changes to return quota delays

[ https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503976#comment-14503976 ] Aditya A Auradkar commented on KAFKA-2136: -- Created reviewboard https://reviews.a

[jira] [Updated] (KAFKA-2136) Client side protocol changes to return quota delays

[ https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya A Auradkar updated KAFKA-2136: - Attachment: KAFKA-2136.patch > Client side protocol changes to return quota delays > -

Re: Review Request 31850: Patch for KAFKA-1660

> On April 20, 2015, 5:30 p.m., Jay Kreps wrote: > > clients/src/main/java/org/apache/kafka/clients/producer/KafkaProducer.java, > > line 526 > > > > > > I cleaned up this javadoc a little bit to try to simplify thing

Re: Review Request 33378: Patch for KAFKA-2136

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33378/ --- (Updated April 21, 2015, 12:02 a.m.) Review request for kafka and Joel Koshy.

Re: Review Request 33378: Patch for KAFKA-2136

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33378/ --- (Updated April 21, 2015, 12:02 a.m.) Review request for kafka and Joel Koshy.

[jira] [Updated] (KAFKA-1910) Refactor KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1910: -- Resolution: Fixed Status: Resolved (was: Patch Available) The follow-up has been committed > R

Re: [DISCUSS] KIP-11- Authorization design for kafka security

According to the pseudo code, if you have a rule "deny user1", then it essentially denies all users? Thanks, Jun On Mon, Apr 20, 2015 at 5:16 PM, Parth Brahmbhatt < pbrahmbh...@hortonworks.com> wrote: > > Here is a pseudo code that explains my current approach: > > acls = authorizer.getAcl(reso

[jira] [Assigned] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-1595: -- Assignee: Ismael Juma > Remove deprecated and slower scala JSON parser from kafka.consumer.Topi

Re: [DISCUSS] KIP-11- Authorization design for kafka security

I admit that I'm also not sure what we gain by having "deny" rules. A user is either in the "allow" list (one way or another) or it will be denied by default. I think this is something we can skip for now and add later if needed? On Mon, Apr 20, 2015 at 5:24 PM, Jun Rao wrote: > According to the

Re: Review Request 31850: Patch for KAFKA-1660

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/31850/ --- (Updated April 21, 2015, 12:38 a.m.) Review request for kafka. Bugs: KAFKA-16

[jira] [Updated] (KAFKA-1660) Ability to call close() with a timeout on the Java Kafka Producer.

[ https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1660: Status: Patch Available (was: In Progress) > Ability to call close() with a timeout on the Java Kaf

[jira] [Updated] (KAFKA-1660) Ability to call close() with a timeout on the Java Kafka Producer.

[ 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-04-20_17:38:22.patch > Ability to call close() with a timeout on the Jav

[jira] [Commented] (KAFKA-1660) Ability to call close() with a timeout on the Java Kafka Producer.

[ https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504039#comment-14504039 ] Jiangjie Qin commented on KAFKA-1660: - Updated reviewboard https://reviews.apache.org/

Review Request 33383: Patch for KAFKA-1595

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

[jira] [Updated] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1595: --- Status: Patch Available (was: Open) > Remove deprecated and slower scala JSON parser from kafka.consu

[jira] [Updated] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1595: --- Attachment: KAFKA-1595.patch > Remove deprecated and slower scala JSON parser from kafka.consumer.Topi

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504055#comment-14504055 ] Ismael Juma commented on KAFKA-1595: Created reviewboard https://reviews.apache.org/r/

[GitHub] kafka pull request: Kafka 1595 remove deprecated json parser

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/55 Kafka 1595 remove deprecated json parser You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-1595-remove-deprecated-json-parser Alte

Re: [DISCUSS] KIP-11- Authorization design for kafka security

 According to the pseudo code, if you have a rule "deny user1", then it  > essentially denies all users?  Gwen,       I see “deny” being useful. I.e you want to allow everyone except few users. This is probably a common case otherwise without deny you have to add long list of users who should be

Re: [DISCUSS] KIP-19 Add a request timeout to NetworkClient

Jun, I thought a little bit differently on this. Intuitively, I am thinking that if a partition is offline, the metadata for that partition should be considered not ready because we don’t know which broker we should send the message to. So those sends need to be blocked on metadata timeout. Anothe

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504095#comment-14504095 ] Ismael Juma commented on KAFKA-1595: Since there were no objections in the mailing lis

Re: [DISCUSS] KIP-11- Authorization design for kafka security

Wouldn't the "everyone except few users" be easier to manage through groups / roles? I think thats how its done in pretty much any system I can think of. Do you know any system with "deny" option? I don't feel strongly about this (i.e. its an extra feature, people can use it or not. maybe it will

[jira] [Commented] (KAFKA-1054) Eliminate Compilation Warnings for 0.8 Final Release

[ https://issues.apache.org/jira/browse/KAFKA-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504099#comment-14504099 ] Ismael Juma commented on KAFKA-1054: Note that there are also some deprecation warning

Can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

Hi dear dev, Need create on KIP with title "Add one configuration log.preallocate" for https://issues.apache.org/jira/browse/KAFKA-1646 But can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

Re: Can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

What is your confluence username? ~ Joe Stein - - - - - - - - - - - - - - - - - http://www.stealth.ly - - - - - - - - - - - - - - - - - On Mon, Apr 20, 2015 at 9:15 PM, Honghai Chen wrote: > Hi dear dev, > > Need create on KIP with title “Add one configuration > log.prealloc

RE: Can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

Username: waldenchen Email:waldenc...@163.com Thanks, Honghai -Original Message- From: Joe Stein [mailto:joe.st...@stealth.ly] Sent: Tuesday, April 21, 2015 9:19 AM To: dev@kafka.apache.org Subject: Re: Can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/

Re: Can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

give it a try now ~ Joe Stein - - - - - - - - - - - - - - - - - http://www.stealth.ly - - - - - - - - - - - - - - - - - On Mon, Apr 20, 2015 at 9:22 PM, Honghai Chen wrote: > Username: waldenchen > Email:waldenc...@163.com > > Thanks, Honghai > > -Original Message- > From: Joe Stein

RE: Can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

It works, many thanks. Thanks, Honghai From: Joe Stein [mailto:joe.st...@stealth.ly] Sent: Tuesday, April 21, 2015 9:24 AM To: Honghai Chen Cc: dev@kafka.apache.org Subject: Re: Can't see "KIP Template" after click Create on https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Pro

[jira] [Assigned] (KAFKA-2132) Move Log4J appender to clients module

[ https://issues.apache.org/jira/browse/KAFKA-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh reassigned KAFKA-2132: - Assignee: Ashish K Singh (was: Gwen Shapira) > Move Log4J appender to clients module > -

[DISCUSS] KIP 20 Enable log preallocate to improve consume performance under windows and some old Linux file system

I wrote a KIP for this after some discussion on KAFKA-1646. https://issues.apache.org/jira/browse/KAFKA-1646 https://cwiki.apache.org/confluence/display/KAFKA/KIP-20+-+Enable+log+preallocate+to+improve+consume+performance+under+windows+and+some+old+Linux+file+system The RB is here: https://reviews

  1   2   >