[jira] [Created] (KAFKA-7724) Docs for KIP-71 compact AND delete need correcting

Antony Stubbs created KAFKA-7724: Summary: Docs for KIP-71 compact AND delete need correcting Key: KAFKA-7724 URL: https://issues.apache.org/jira/browse/KAFKA-7724 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-7725) Add a delay for further CG rebalances, beyond KIP-134 group.initial.rebalance.delay.ms

Antony Stubbs created KAFKA-7725: Summary: Add a delay for further CG rebalances, beyond KIP-134 group.initial.rebalance.delay.ms Key: KAFKA-7725 URL: https://issues.apache.org/jira/browse/KAFKA-7725

[jira] [Reopened] (KAFKA-4790) Kafka cannot recover after a disk full

[ https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reopened KAFKA-4790: - > Kafka cannot recover after a disk full > -- > >

Re: Vote for KIP-393 (Fix time windowed serde to deserialize changelog topic)

+1 (non-binding) from me. Looks like a pretty clear-cut case. On Tue, Dec 11, 2018 at 1:11 AM Shawn Nguyen wrote: > Thanks for the feedback Guozhang! I updated the KIP. > > In the meantime, could I ask for additional binding votes/approval on this > KIP proposal? > > Shawn > > On Thu, Dec 6, 2

[jira] [Created] (KAFKA-7726) Connector status on deletion

Eyal Ringort created KAFKA-7726: --- Summary: Connector status on deletion Key: KAFKA-7726 URL: https://issues.apache.org/jira/browse/KAFKA-7726 Project: Kafka Issue Type: Bug Components

RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions in KafkaConsumer

Hi Mayuresh, Thanks for the input! Pausing and Resuming are cumbersome and has some undesirable performance impact since pausing will in effect clean up the completed fetch and resuming will call the broker to retrieve again. The way I changed the code was just to parse the completed fetch ea

[jira] [Created] (KAFKA-7727) kafka-producer-network-thread throwing Error: NOT_LEADER_FOR_PARTITION after adding new broker to kafka cluster

venkatakumar puvvada created KAFKA-7727: --- Summary: kafka-producer-network-thread throwing Error: NOT_LEADER_FOR_PARTITION after adding new broker to kafka cluster Key: KAFKA-7727 URL: https://issues.apache.

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

Hey Jason, Yes, that is what I meant by > Given those constraints, I think that we can simply mark the group as `PreparingRebalance` with a rebalanceTimeout of the server setting ` group.max.session.timeout.ms`. That's a bit long by default (5 minutes) but I can't seem to come up with a better alt

Permissions to edit KIP page and ...

Hi I used to have permissions to edit KIP page (https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals). Now suddenly I do not. I created KIP-381 and now wanted to change to put it into vote mode. I cannot edit neither KIP page nor KIP-381 page. Please give me permissio

Re: Permissions to edit KIP page and ...

I just gave you permissions. Thanks. On Wed, Dec 12, 2018 at 7:50 PM Per Steffensen wrote: > Hi > > I used to have permissions to edit KIP page > ( > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals). > > Now suddenly I do not. I created KIP-381 and now wanted to cha

[VOTE] KIP-381 Connect: Tell about records that had their offsets flushed in callback

Hope for your votes

RE: [DISCUSS] KIP-382: MirrorMaker 2.0

Ryanne, You haven’t described how one would handle the ordering issues and also the compaction issues where transactional processing is master-master in regions, where the processing is sticky to region but of failure or planned, processing of certain accounts move regions. Also I ask that you

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

> Wikimedia currently implements 'master <-> master' replication by manually prefixing topics with datacenter names, and then configuring MirrorMaker to only replicate topics that begin with a DC name to another. Andrew, this is a common approach and solves some of the problems I've mentioned, but

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

> You haven’t described how one would handle the ordering issues and also the compaction issues where transactional processing is master-master in regions, where the processing is sticky to region but of failure or planned, processing of certain accounts move regions. Michael, a couple points: -

[jira] [Resolved] (KAFKA-7705) Update javadoc for the values of delivery.timeout.ms or linger.ms

[ https://issues.apache.org/jira/browse/KAFKA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7705. Resolution: Fixed Fix Version/s: 2.1.1 > Update javadoc for the values of delivery.t

Re: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions in KafkaConsumer

Hi ChienHsing, We are actually working on buffering the already fetched data for paused topicPartitions, so ideally it should not have any effect on performance. Associated jira : https://issues.apache.org/jira/browse/KAFKA-7548 Thanks, Mayuresh On Wed, Dec 12, 2018 at 6:01 AM ChienHsing Wu wr

RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions in KafkaConsumer

Good to know that, Thanks! Nonetheless, that introduces additional complexity at the client side for a common expectation to more or less receives records in a fair fashion. CH -Original Message- From: Mayuresh Gharat Sent: Wednesday, December 12, 2018 12:55 PM To: dev@kafka.apache.o

[jira] [Resolved] (KAFKA-7712) Handle exceptions from immediately connected channels in Selector

[ https://issues.apache.org/jira/browse/KAFKA-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7712. Resolution: Fixed > Handle exceptions from immediately connected channels in Selector > ---

Kafka Trunk Build Failure with Gradle 5.0

Hey friends, I'm wondering anyone has seen this error before: Could not find method annotationProcessor() for arguments [org.openjdk.jmh:jmh-generator-annprocess:1.21] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler. Basically I'm building the trun

Build failed in Jenkins: kafka-2.1-jdk8 #81

See Changes: [jason] KAFKA-7705; Fix and simplify producer config in javadoc example (#6000) -- [...truncated 910.09 KB...] kafka.security.auth.SimpleAclAuthorizerTest > test

RE: [DISCUSS] KIP-382: MirrorMaker 2.0

Ok so you have your transaction system running master master. You have three dcs, regions where-ever. Accounts are distributed across area based on an number of factors Account A + B are in Ireland Account C + D are in Germany Account E are in UK Lets prefix call kafka cluster in Ireland Z, Ger

Re: Kafka Trunk Build Failure with Gradle 5.0

I used to see your issue but I was on an older version of gradle and we upgraded to 4.8.1. On gradle 5.0 that issue goes away on my box: guozhang @kafka-work: gradle --version Gradle 5.0

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Hi Adam, Given that the committers are all pretty busy right now, I think that it would help if you were to refactor the KIP a little to reduce the workload for reviewers. I'd recommend the following changes: * relocate all internal details to a section at the end called something like "Implement

[jira] [Resolved] (KAFKA-5386) [Kafka Streams] - custom name for state-store change-log topic

[ https://issues.apache.org/jira/browse/KAFKA-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5386. -- Resolution: Fixed Fix Version/s: 1.0.0 > [Kafka Streams] - custom name for state-store c

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

> Consuming system restarts and restates from compacted topics, using *.account_state Michael, I think I understand your concern. With MM2's remote topic concept, it's the consumer's responsibility to aggregate records across .*account_state. MM2 will not merge these for you (by design). This comp

Build failed in Jenkins: kafka-2.1-jdk8 #82

See Changes: [jason] KAFKA-7616; Make MockConsumer only add entries to the partition map -- [...truncated 922.45 KB...]

[DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Hi all, I would like to start a discussing for the following KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-404%3A+Add+Kafka+Connect+configuration+parameter+for+disabling+WADL+output+on+OPTIONS+request . The KIP proposes to add a configuration parameter for Connect Worker, which would

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Alex, Thanks for putting up this KIP. The proposal lgtm. Guozhang On Wed, Dec 12, 2018 at 7:41 PM Oleksandr Diachenko wrote: > Hi all, > > I would like to start a discussing for the following KIP: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-404%3A+Add+Kafka+Connect+configuration+

[jira] [Created] (KAFKA-7728) Add JoinReason to the join group request for better rebalance handling

Boyang Chen created KAFKA-7728: -- Summary: Add JoinReason to the join group request for better rebalance handling Key: KAFKA-7728 URL: https://issues.apache.org/jira/browse/KAFKA-7728 Project: Kafka

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hi Ryanne, Thanks for the KIP. In general, I think the proposal makes a lot of sense to me. Unifying Kafka clusters in different locations has been a very important scenario. Right now open source community does not have a standard solution to that. A few comments/questions are following: 1. Onl

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

See Changes: [wangguoz] KAFKA-7223: document suppression buffer metrics (#6024) -- [...truncated 4.48 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldPas