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

See Changes: [junrao] KAFKA-2946; MINOR: Follow up. Add Delete to AclCommandTest -- [...truncated 12205 lines...] org.apache.kafka.streams.processor.internals.MinTimestampTrackerTest >

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

See Changes: [junrao] KAFKA-2946; MINOR: Follow up. Add Delete to AclCommandTest -- [...truncated 12167 lines...] org.apache.kafka.streams.processor.internals.MinTimestampTrackerTest >

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

See Changes: [ismael] KAFKA-4034; Avoid unnecessary consumer coordinator lookup -- [...truncated 12204 lines...] org.apache.kafka.streams.processor.internals.MinTimestampTrackerTest >

Re: [DISCUSS] KIP-75 - Add per-connector Converters

+1 On Fri, Aug 12, 2016 at 7:36 PM, Gwen Shapira wrote: > Looks good to me too - simple, usable and the use-case is clear. > > Gwen > > On Fri, Aug 12, 2016 at 12:56 PM, Ewen Cheslack-Postava > wrote: > > Hi all, > > > > I've added KIP-75 - Add

Re: [DISCUSS] KIP-75 - Add per-connector Converters

Looks good to me too - simple, usable and the use-case is clear. Gwen On Fri, Aug 12, 2016 at 12:56 PM, Ewen Cheslack-Postava wrote: > Hi all, > > I've added KIP-75 - Add per-connector Converters > >

Re: How to get pull request reviewed - Pull request # 1539

Hey, In the case of your specific PR, there is also a KIP. Which means we go by the KIP process: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals It looks like you followed steps #1 and #2 in the process (create the wiki), now its time for step #3 - start a

Re: [DISCUSS] Time-based releases for Apache Kafka

Thats good feedback, thanks. I don't think you were involved in the previous release, but we did try to follow the model you suggest. We announced few weeks before cutting branches and gave time for features and stabilization. This started a mad last-minute rush of semi-baked features that forced

[jira] [Commented] (KAFKA-2946) DeleteTopic - protocol and server side implementation

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

[GitHub] kafka pull request #1732: MINOR: Clarification in producer config documentat...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1732 MINOR: Clarification in producer config documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka

[jira] [Updated] (KAFKA-4034) Consumer need not lookup coordinator when using manual assignment

[ https://issues.apache.org/jira/browse/KAFKA-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4034: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 0.10.1.0 > Consumer

[jira] [Updated] (KAFKA-4034) Consumer need not lookup coordinator when using manual assignment

[ https://issues.apache.org/jira/browse/KAFKA-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4034: --- Status: Patch Available (was: Open) > Consumer need not lookup coordinator when using manual

[jira] [Updated] (KAFKA-4034) Consumer need not lookup coordinator when using manual assignment

[ https://issues.apache.org/jira/browse/KAFKA-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4034: --- Fix Version/s: 0.10.0.1 > Consumer need not lookup coordinator when using manual assignment >

[jira] [Commented] (KAFKA-4034) Consumer need not lookup coordinator when using manual assignment

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

[GitHub] kafka pull request #1720: KAFKA-4034: Avoid unnecessary consumer coordinator...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1720 --- 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

[GitHub] kafka pull request #1731: MINOR: add slf4jlog4j to streams example

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1731 MINOR: add slf4jlog4j to streams example You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka Kminor-log4j-streams-examples

[GitHub] kafka pull request #1729: Assign ConfigDef.NO_DEFAULT_VALUE as a literal, us...

Github user shikhar closed the pull request at: https://github.com/apache/kafka/pull/1729 --- 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

[jira] [Commented] (KAFKA-2946) DeleteTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419628#comment-15419628 ] ASF GitHub Bot commented on KAFKA-2946: --- GitHub user granthenke opened a pull request:

[GitHub] kafka pull request #1729: Assign ConfigDef.NO_DEFAULT_VALUE as a literal, us...

GitHub user shikhar opened a pull request: https://github.com/apache/kafka/pull/1729 Assign ConfigDef.NO_DEFAULT_VALUE as a literal, use equals() for comp… …arison rather than == You can merge this pull request into a Git repository by running: $ git pull

[GitHub] kafka pull request #1730: MINOR: KAFKA-2946 Follow up. Add Delete to AclComm...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1730 MINOR: KAFKA-2946 Follow up. Add Delete to AclCommandTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka test-delete

[jira] [Commented] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

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

[jira] [Updated] (KAFKA-4012) KerberosShortNamer should implement toString()

[ https://issues.apache.org/jira/browse/KAFKA-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4012: --- Resolution: Fixed Status: Resolved (was: Patch Available) > KerberosShortNamer should

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3997: --- Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was: Patch Available)

[jira] [Updated] (KAFKA-4012) KerberosShortNamer should implement toString()

[ https://issues.apache.org/jira/browse/KAFKA-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4012: --- Fix Version/s: 0.10.1.0 > KerberosShortNamer should implement toString() >

[GitHub] kafka pull request #1724: KAFKA-3997: log partition name on truncation

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1724 --- 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

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419587#comment-15419587 ] Onur Karaman commented on KAFKA-3959: - [~granthenke] maybe in the long term. But honestly I would

[GitHub] kafka pull request #1728: MINOR: add describe to valid group acl operations

Github user norwood closed the pull request at: https://github.com/apache/kafka/pull/1728 --- 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

[jira] [Commented] (KAFKA-4012) KerberosShortNamer should implement toString()

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

[GitHub] kafka pull request #1694: KAFKA-4012: Added #toString() to KerberosShortName...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1694 --- 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

[GitHub] kafka pull request #1728: MINOR: add describe to valid group acl operations

GitHub user norwood opened a pull request: https://github.com/apache/kafka/pull/1728 MINOR: add describe to valid group acl operations @junrao You can merge this pull request into a Git repository by running: $ git pull https://github.com/norwood/kafka

Re: [DISCUSS] Time-based releases for Apache Kafka

I'm not convinced that time-based releases for this type of development are the right thing. Something like Ubuntu, where all components are moving targets needs to decide to freeze and release without having full coordination from the participants. There is no guarantee from Canonical that the

Re: [DISCUSS] Time-based releases for Apache Kafka

Interesting, so you are suggesting that we drop Kafka's current versioning scheme (0.major.minor.patch)? I can see the reasoning for doing so now. However, I think I'd prefer to do that when we do the 1.x bump, which I think we should do once exactly-once lands. That way people only have to

[jira] [Commented] (KAFKA-2946) DeleteTopic - protocol and server side implementation

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

[GitHub] kafka pull request #1616: KAFKA-2946: DeleteTopic - protocol and server side...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1616 --- 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

[jira] [Updated] (KAFKA-2946) DeleteTopic - protocol and server side implementation

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

Re: [DISCUSS] Time-based releases for Apache Kafka

Right now, our major releases are really indicated in the second digit, not in the leading 0. So 0.10 is a major, 0.10.1 is a minor and 0.10.0.1 is a bug fix. Thanks, Jun On Fri, Aug 12, 2016 at 1:17 PM, Gwen Shapira wrote: > Good question! > > My thoughts are... bugfix

[jira] [Commented] (KAFKA-3408) consumer rebalance fail

[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419489#comment-15419489 ] Ewen Cheslack-Postava commented on KAFKA-3408: -- [~dpnchl] I've added you as a contributor to

[jira] [Commented] (KAFKA-3847) Connect tasks should not share a producer

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

[jira] [Updated] (KAFKA-3847) Connect tasks should not share a producer

[ https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3847: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request #1727: KAFKA-3847: Use a separate producer per source tas...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1727 --- 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

Kafka Mirror maker duplicate issue

Hi there, I created a broker as stand by using Kafka Mirror maker but same messages gets consumed by both Source broker and mirror broker. Ex: I send 1000 messages let's say offset value 1 to 1000 and consumed 500 messages from the source broker. Now my broker goes down and want to read rest

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419471#comment-15419471 ] Grant Henke commented on KAFKA-3959: I would like to present an alternative option. This problem

[jira] [Created] (KAFKA-4036) Unsafe dictionary access in VerifiableConsumer service

Jason Gustafson created KAFKA-4036: -- Summary: Unsafe dictionary access in VerifiableConsumer service Key: KAFKA-4036 URL: https://issues.apache.org/jira/browse/KAFKA-4036 Project: Kafka

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419441#comment-15419441 ] Onur Karaman commented on KAFKA-3959: - btw I can pick this one up once we agree on the fix. >

[jira] [Commented] (KAFKA-3408) consumer rebalance fail

[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419429#comment-15419429 ] Amey commented on KAFKA-3408: - I also tried but can't reproduce this. Surely we can collaborate on this, once

Stream processing meetup at LinkedIn (Mountain View) on Tuesday, August 23 at 6pm

Hi everyone, We would like to invite you to a Stream Processing Meetup at LinkedIn’s *Mountain View campus on Tuesday, August 23 at 6pm*. Please RSVP here (only if you intend to attend in person): https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/232864129 We have three great talks

[jira] [Commented] (KAFKA-3408) consumer rebalance fail

[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419424#comment-15419424 ] kambiz shahri commented on KAFKA-3408: -- Yes sure. > consumer rebalance fail >

Re: [DISCUSS] Time-based releases for Apache Kafka

Good question! My thoughts are... bugfix releases will be done "as needed" based on community feedback Feature releases will be a minor release by default 0.11, 0.12 - unless: 1. We manage to break compatibility completely (we shouldn't) in which case we need to bump to 1.X 2. We do something

Re: [DISCUSS] KIP-75 - Add per-connector Converters

Sounds sensible to me. Ismael On Fri, Aug 12, 2016 at 8:56 PM, Ewen Cheslack-Postava wrote: > Hi all, > > I've added KIP-75 - Add per-connector Converters > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 75+-+Add+per-connector+Converters > > This is a very small

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419365#comment-15419365 ] Todd Palino commented on KAFKA-3959: Agree with Onur 100% here. We've been running into this a lot

[DISCUSS] KIP-75 - Add per-connector Converters

Hi all, I've added KIP-75 - Add per-connector Converters https://cwiki.apache.org/confluence/display/KAFKA/KIP-75+-+Add+per-connector+Converters This is a very small completely backwards compatible change, a patch is already available https://github.com/apache/kafka/pull/1721, and I think

[jira] [Commented] (KAFKA-4032) Uncaught exceptions when autocreating topics

[ https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419350#comment-15419350 ] Grant Henke commented on KAFKA-4032: I will make a patch for this shortly > Uncaught exceptions when

[jira] [Assigned] (KAFKA-4032) Uncaught exceptions when autocreating topics

[ https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke reassigned KAFKA-4032: -- Assignee: Grant Henke > Uncaught exceptions when autocreating topics >

[jira] [Commented] (KAFKA-4032) Uncaught exceptions when autocreating topics

[ https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419348#comment-15419348 ] Ismael Juma commented on KAFKA-4032: cc [~granthenke] > Uncaught exceptions when autocreating topics

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

Hey Damian, That's true, but it would avoid the need to write tombstones for the expired offsets I guess. I'm actually not sure it's a great idea anyway. One thing we've talked about is not expiring any offsets as long as a group is alive, which would require some custom expiration logic. There's

[jira] [Commented] (KAFKA-3847) Connect tasks should not share a producer

[ https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419261#comment-15419261 ] ASF GitHub Bot commented on KAFKA-3847: --- GitHub user ewencp opened a pull request:

[jira] [Updated] (KAFKA-3847) Connect tasks should not share a producer

[ https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3847: - Status: Patch Available (was: Open) > Connect tasks should not share a producer

[jira] [Commented] (KAFKA-4033) KIP-70: Revise Partition Assignment Semantics on New Consumer's Subscription Change

[ https://issues.apache.org/jira/browse/KAFKA-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419250#comment-15419250 ] ASF GitHub Bot commented on KAFKA-4033: --- GitHub user vahidhashemian opened a pull request:

[GitHub] kafka pull request #1725: WIP KAFKA-3894: split log segment to avoid crashin...

GitHub user tcrayford opened a pull request: https://github.com/apache/kafka/pull/1725 WIP KAFKA-3894: split log segment to avoid crashing cleaner thread https://issues.apache.org/jira/browse/KAFKA-3894 This is a temporary PR, to see what Jenkins has to say about this work

Re: [DISCUSS] Time-based releases for Apache Kafka

​How would time releases relate to versions? (Major, minor, API compatibility, etc).​ On Thu, Aug 11, 2016 at 9:37 AM, Guozhang Wang wrote: > I think we do not need to make the same guarantee as for "how old of your > Kafka version that you can upgrade to the latest in one

[jira] [Commented] (KAFKA-3408) consumer rebalance fail

[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419157#comment-15419157 ] Dru P commented on KAFKA-3408: -- [~sdhzlzhk] The information you've provided is insufficient to reproduce the

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419140#comment-15419140 ] Manikumar Reddy commented on KAFKA-3959: Yes, min.insync.replicas applicable to internal topics

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419134#comment-15419134 ] Sriharsha Chintalapani commented on KAFKA-2629: --- [~singhashish] happy to review and get this

Re: Review request for KAFKA-3600

I think one of the hard parts is that while we agree that a call to ApiVersions is required, I don't think there is agreement on how to use the response. In kafka-python, for example, to support backwards compatibility we set a single "api" configuration value during the client constructor. This

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419124#comment-15419124 ] Onur Karaman commented on KAFKA-3959: - Another options is to offload the responsibility of

[jira] [Commented] (KAFKA-3545) Generalized Serdes for List/Map

[ https://issues.apache.org/jira/browse/KAFKA-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419116#comment-15419116 ] Dru P commented on KAFKA-3545: -- [~gfodor] and [~guozhang] - How can I contribute to this project? I've read

Re: [DISCUSS] KIP-74: Add Fetch Response Size Limit in Bytes

Hi! > On 12 Aug 2016, at 18:32, Jun Rao wrote: > > Hi, Andrey, > > Why shouldn't the client library do reordering? It seems that if > ReplicaFetcher thread does round-robin, the consumer client should do that > too? > IMHO the client library is not a good place to

[jira] [Comment Edited] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419066#comment-15419066 ] James Cheng edited comment on KAFKA-3959 at 8/12/16 4:12 PM: - You mentioned

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419066#comment-15419066 ] James Cheng commented on KAFKA-3959: You mentioned {bq} but __consumer_offsets append still will fail

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419057#comment-15419057 ] Onur Karaman commented on KAFKA-3959: - Perfect timing! [~toddpalino] and I hit this behavior again on

How to get pull request reviewed - Pull request # 1539

Hi All, I am new to the Kafka community group development and was wondering how do I get my pull request reviewed/processed? https://github.com/apache/kafka/pull/1539 Am I missing any steps or is it just the backlog? Thanks,Jayesh

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

Thanks Jun On Fri, 12 Aug 2016 at 16:41 Jun Rao wrote: > Hi, Damian, > > I was just wondering if we should disable size-based retention in the > compact_and_delete mode. So, it sounds like that there could be a use case > for that. Since by default, the size-based retention

[jira] [Commented] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419025#comment-15419025 ] ASF GitHub Bot commented on KAFKA-3997: --- GitHub user resetius opened a pull request:

[GitHub] kafka pull request #1724: [KAFKA-3997] log partition name on truncation

GitHub user resetius opened a pull request: https://github.com/apache/kafka/pull/1724 [KAFKA-3997] log partition name on truncation You can merge this pull request into a Git repository by running: $ git pull https://github.com/resetius/kafka KAFKA-3997 Alternatively you can

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

Hi, Damian, I was just wondering if we should disable size-based retention in the compact_and_delete mode. So, it sounds like that there could be a use case for that. Since by default, the size-based retention is infinite, I think we can just leave the KIP as it is. Thanks, Jun On Fri, Aug 12,

Re: [DISCUSS] KIP-74: Add Fetch Response Size Limit in Bytes

Hi, Andrey, Why shouldn't the client library do reordering? It seems that if ReplicaFetcher thread does round-robin, the consumer client should do that too? Thanks, Jun On Fri, Aug 12, 2016 at 3:56 AM, Andrey L. Neporada < anepor...@yandex-team.ru> wrote: > Hi! > > > On 12 Aug 2016, at 04:29,

Would like to start contributing to Kafka project

Hi, Can you add me as a contributor to the Kafka project. Thanks Shashank

[jira] [Commented] (KAFKA-3991) MirrorMaker: allow custom publisher

[ https://issues.apache.org/jira/browse/KAFKA-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418966#comment-15418966 ] ASF GitHub Bot commented on KAFKA-3991: --- GitHub user hsun-cnnxty reopened a pull request:

[GitHub] kafka pull request #1666: [KAFKA-3991]: allow MirrorMaker to have custom pro...

GitHub user hsun-cnnxty reopened a pull request: https://github.com/apache/kafka/pull/1666 [KAFKA-3991]: allow MirrorMaker to have custom producer Please see jira: https://issues.apache.org/jira/browse/KAFKA-3991 You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-3991) MirrorMaker: allow custom publisher

[ https://issues.apache.org/jira/browse/KAFKA-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418965#comment-15418965 ] ASF GitHub Bot commented on KAFKA-3991: --- Github user hsun-cnnxty closed the pull request at:

[GitHub] kafka pull request #1666: [KAFKA-3991]: allow MirrorMaker to have custom pro...

Github user hsun-cnnxty closed the pull request at: https://github.com/apache/kafka/pull/1666 --- 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

[jira] [Updated] (KAFKA-4012) KerberosShortNamer should implement toString()

[ https://issues.apache.org/jira/browse/KAFKA-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-4012: --- Status: Patch Available (was: Open) > KerberosShortNamer should implement toString() >

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418943#comment-15418943 ] Ashish K Singh commented on KAFKA-2629: --- [~harsha_ch] any thoughts? > Enable getting SSL password

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418941#comment-15418941 ] Ashish K Singh commented on KAFKA-2629: --- [~bharatviswa] the way we do it is that for password

Re: Review request for KAFKA-3600

Most of the work in the patch is to enhance NetworkClient to maintain api versions supported by brokers it has connections to. When a broker disconnects, its api versions info is removed and when it reconnects that info is fetched again. In short, with these changes Network Client at any given

[jira] [Updated] (KAFKA-4035) AclCommand should allow Describe operation on groups

[ https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-4035: --- Affects Version/s: 0.9.0.0 0.10.0.0 0.10.0.1 >

[jira] [Updated] (KAFKA-4035) AclCommand should allow Describe operation on groups

[ https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-4035: --- Status: Patch Available (was: Open) > AclCommand should allow Describe operation on groups >

[jira] [Commented] (KAFKA-4035) AclCommand should allow Describe operation on groups

[ https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418906#comment-15418906 ] ASF GitHub Bot commented on KAFKA-4035: --- GitHub user omkreddy opened a pull request:

[GitHub] kafka pull request #1723: KAFKA-4035: AclCommand should allow Describe opera...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1723 KAFKA-4035: AclCommand should allow Describe operation on groups You can merge this pull request into a Git repository by running: $ git pull https://github.com/omkreddy/kafka KAFKA-4035

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

Hi Jason, It is still not clear to me how adding a callback would help. You could remove the periodic task, but you would still need to scan the entire cache to remove the expired offsets. Am i missing something? Thanks, Damian On 11 August 2016 at 10:00, Damian Guy

[jira] [Commented] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418836#comment-15418836 ] William Yu commented on KAFKA-3937: --- FYI: My brokers and client are both on kafka: 0.9.0.1. > Kafka

[jira] [Assigned] (KAFKA-4035) AclCommand should allow Describe operation on groups

[ https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-4035: -- Assignee: Manikumar Reddy > AclCommand should allow Describe operation on groups >

[jira] [Comment Edited] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418751#comment-15418751 ] Manikumar Reddy edited comment on KAFKA-3959 at 8/12/16 1:27 PM: - looks

[jira] [Commented] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418824#comment-15418824 ] Ismael Juma commented on KAFKA-3937: Seems like this one then. It's the first time we're hearing about

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418819#comment-15418819 ] Ismael Juma commented on KAFKA-3959: The current behaviour "minimum of (available brokers,

[jira] [Commented] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418766#comment-15418766 ] William Yu commented on KAFKA-3937: --- [~ijuma], yes the topic is compressed, are producer is setup with

[jira] [Comment Edited] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418766#comment-15418766 ] William Yu edited comment on KAFKA-3937 at 8/12/16 12:43 PM: - [~ijuma], yes

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418751#comment-15418751 ] Manikumar Reddy commented on KAFKA-3959: looks like this is done on purpose. While creating

[jira] [Resolved] (KAFKA-4031) Check DirectBuffer's cleaner to be not null before using

[ https://issues.apache.org/jira/browse/KAFKA-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4031. Resolution: Fixed Reviewer: Ismael Juma > Check DirectBuffer's cleaner to be not null before

[jira] [Updated] (KAFKA-4031) Check DirectBuffer's cleaner to be not null before using

[ https://issues.apache.org/jira/browse/KAFKA-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4031: --- Fix Version/s: (was: 0.10.0.2) 0.10.1.0 > Check DirectBuffer's cleaner to be

[jira] [Commented] (KAFKA-4031) Check DirectBuffer's cleaner to be not null before using

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

  1   2   >