Re: Pluggable Log Compaction Policy

Hello again, Is there anyone on this thread who has admin access to the Kafka Confluence wiki? I want to create a KIP but I don't have permissions to actually create a page. Bill On Fri, Jan 22, 2016 at 3:29 PM, Guozhang Wang wrote: > Bill, > > Sounds good. If you want to drive pushing this f

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125212#comment-15125212 ] Sriharsha Chintalapani commented on KAFKA-1696: --- [~singhashish] We are worki

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125186#comment-15125186 ] Jiangjie Qin commented on KAFKA-3174: - Thanks for the info [~gwenshap]. We have also b

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125180#comment-15125180 ] Jiangjie Qin commented on KAFKA-3177: - [~hachikuji] [~guozhang] Not sure what is the c

[jira] [Created] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

Jiangjie Qin created KAFKA-3177: --- Summary: Kafka consumer can hang when position() is called on a non-existing partition. Key: KAFKA-3177 URL: https://issues.apache.org/jira/browse/KAFKA-3177 Project: K

Build failed in Jenkins: kafka-trunk-jdk8 #332

See Changes: [cshapi] KAFKA-3164: Document client and mirrormaker upgrade procedure/require… -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on

Build failed in Jenkins: kafka_0.9.0_jdk7 #107

See Changes: [cshapi] KAFKA-3164: Document client and mirrormaker upgrade procedure/require… -- [...truncated 1502 lines...] kafka.integration.SaslSslTopicMetadataTest > testBasicTopicMetadata

[jira] [Created] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

Jiangjie Qin created KAFKA-3176: --- Summary: Allow console consumer to consume from particular partitions when new consumer is used. Key: KAFKA-3176 URL: https://issues.apache.org/jira/browse/KAFKA-3176 P

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125169#comment-15125169 ] Ismael Juma commented on KAFKA-3174: That's good to know Gwen. Still, we were recommen

Build failed in Jenkins: kafka-trunk-jdk7 #1005

See Changes: [cshapi] KAFKA-3164: Document client and mirrormaker upgrade procedure/require… -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on

[jira] [Updated] (KAFKA-3164) Document client and mirrormaker upgrade procedure/requirements

[ https://issues.apache.org/jira/browse/KAFKA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3164: Resolution: Fixed Reviewer: Gwen Shapira Fix Version/s: 0.9.1.0 0.

[jira] [Commented] (KAFKA-3164) Document client and mirrormaker upgrade procedure/requirements

[ https://issues.apache.org/jira/browse/KAFKA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125159#comment-15125159 ] ASF GitHub Bot commented on KAFKA-3164: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-3164: Document client and mirrormaker up...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/838 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125158#comment-15125158 ] Gwen Shapira commented on KAFKA-3174: - As anecdotal evidence, 100% of the customers I

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

I want to second Harsha's approach. Configuration is usually much easier to configure and troubleshoot than protocol-negotiation-protocols, which we've been doing our best to generally avoid in Kafka due to operational complexity. Gwen On Sat, Jan 30, 2016 at 3:32 AM, Harsha wrote: > Rajini, >

Re: Contributor List

Added. Looking forward to your contributions :) On Fri, Jan 29, 2016 at 2:10 PM, Abraham Fine wrote: > Would it be possible to add me to the contributor list? My apache jira > username is: abrahamfine > > Thanks, > Abe

[jira] [Commented] (KAFKA-1696) Kafka should be able to generate Hadoop delegation tokens

[ https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125002#comment-15125002 ] Ashish K Singh commented on KAFKA-1696: --- [~parth.brahmbhatt] just curious if you hav

Re: [DISCUSS] KIP-42: Add Producer and Consumer Interceptors

Nice finding on the CRC class. It will be great to switch to that at some point. On exposing the CRC - I think we are overthinking the problem. CRC over the entire record makes sense for the durability check and having multiple CRCs is a bad idea. On Fri, Jan 29, 2016 at 4:47 PM, Jay Kreps wrote

[jira] [Commented] (KAFKA-2986) Consumer group doesn't lend itself well for slow consumers with varying message size

[ https://issues.apache.org/jira/browse/KAFKA-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124913#comment-15124913 ] Jens Rantil commented on KAFKA-2986: KIP 41 has since last week been passed in on the

Build failed in Jenkins: kafka-trunk-jdk8 #331

See Changes: [harsha] KAFKA-3169; Limit receive buffer size for SASL packets in broker -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (dock

Build failed in Jenkins: kafka-trunk-jdk7 #1004

See Changes: [harsha] KAFKA-3169; Limit receive buffer size for SASL packets in broker -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (doc

[jira] [Commented] (KAFKA-3169) Kafka broker throws OutOfMemory error with invalid SASL packet

[ https://issues.apache.org/jira/browse/KAFKA-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124854#comment-15124854 ] ASF GitHub Bot commented on KAFKA-3169: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-3169: Limit receive buffer size for SASL...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/831 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Rajini, Whats the need for server returning acceptable mechs as network package. Why not drive it through the JAAS file itself. I don't see handshake any different than what it is now and only login will change and it can be configured based on the

[jira] [Resolved] (KAFKA-2679) Mirror Maker produces duplicated data

[ https://issues.apache.org/jira/browse/KAFKA-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] He Tianyi resolved KAFKA-2679. -- Resolution: Not A Problem > Mirror Maker produces duplicated data >

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124813#comment-15124813 ] Ismael Juma commented on KAFKA-3174: Great, left a comment in the PR. > Re-evaluate t