Re: [VOTE] 2.6.1 RC3

+1 (binding) Verified signatures, ran tests from source build (one flaky test failed but passed on rerun), ran Kafka quick start with the binary with both Scala 2.12 and Scala 2.13. Thanks for running the release, Mickael! Regards, Rajini On Fri, Dec 11, 2020 at 3:23 PM Mickael Maison wrote:

Re: [VOTE] KIP-690: Add additional configuration to control MirrorMaker 2 internal topics naming convention

If anyone interested in reading the discussions you can find it here https://www.mail-archive.com/dev@kafka.apache.org/msg113373.html On Tue, Dec 8, 2020 at 4:01 PM Omnia Ibrahim wrote: > Hi everyone, > I’m proposing a new KIP for MirrorMaker 2 to add the ability to control > internal topics

[jira] [Created] (KAFKA-10857) Mirror Maker 2 - replication not working when deploying multiple instances

Athanasios Fanos created KAFKA-10857: Summary: Mirror Maker 2 - replication not working when deploying multiple instances Key: KAFKA-10857 URL: https://issues.apache.org/jira/browse/KAFKA-10857

Improving crash-restart catchup speed

Hi. When a broker crashes and restarts after a long time (say 30 minutes), the broker has to do some work to sync all its replicas with the leaders. If the broker is a preferred replica for some partition, the broker may become the leader as part of a preferred replica leader election, while it

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hi Colin, The KIP says that "brokers which are fenced will not appear in MetadataResponses. So clients that have up-to-date metadata will not try to contact fenced brokers.", which is fine, but it doesn't seem to elaborate on what happens for clients which try to contact a broker (using stale

Jenkins build is back to normal : Kafka » kafka-trunk-jdk8 #288

See

[jira] [Resolved] (KAFKA-10525) Emit JSONs with new auto-generated schema

[ https://issues.apache.org/jira/browse/KAFKA-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10525. - Fix Version/s: 2.8.0 Resolution: Fixed > Emit JSONs with new auto-generated schema >

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #289

See Changes: [github] KAFKA-10525: Emit JSONs with new auto-generated schema (KIP-673) (#9526) [github] KAFKA-10854: fix flaky testConnectionRatePerIp test (#9752)

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #314

See Changes: [github] KAFKA-10525: Emit JSONs with new auto-generated schema (KIP-673) (#9526) [github] KAFKA-10854: fix flaky testConnectionRatePerIp test (#9752)

[jira] [Resolved] (KAFKA-10852) AlterIsr should not be throttled

[ https://issues.apache.org/jira/browse/KAFKA-10852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-10852. - Fix Version/s: 2.7.1 2.8.0 Resolution: Fixed > AlterIsr should not be

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

On Tue, Dec 15, 2020, at 04:13, Tom Bentley wrote: > Hi Colin, > > The KIP says that "brokers which are fenced will not appear in > MetadataResponses. So clients that have up-to-date metadata will not try > to contact fenced brokers.", which is fine, but it doesn't seem to > elaborate on what

Re: [VOTE] voting on KIP-631: the quorum-based Kafka controller

Colin, thanks for driving this. I just read through the KIP again and I think it is in good shape. Exciting stuff! +1 binding -David On Sat, Dec 12, 2020 at 7:46 AM Ron Dagostino wrote: > Thanks for shepherding this KIP through the extended discussion, Colin. I > think we’ve ended up in a

Re: [VOTE] voting on KIP-631: the quorum-based Kafka controller

Thanks Colin for the great work to polish the KIP and reach this final stage. +1 (binding) from me On Tue, Dec 15, 2020 at 9:11 AM David Arthur wrote: > Colin, thanks for driving this. I just read through the KIP again and I > think it is in good shape. Exciting stuff! > > +1 binding > > -David

[jira] [Resolved] (KAFKA-10854) Fix flaky kafka.network.SocketServerTest.testConnectionRatePerIp test

[ https://issues.apache.org/jira/browse/KAFKA-10854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10854. - Fix Version/s: 2.8.0 Resolution: Fixed > Fix flaky

Re: [VOTE] 2.7.0 RC5

Thanks for voting Guozhang. Including the dev list as well. On Mon, Dec 14, 2020 at 5:59 PM Guozhang Wang wrote: > I checked the docs and ran unit tests, no red flags found. +1. > > On Fri, Dec 11, 2020 at 5:45 AM Bill Bejeck wrote: > > > Updated with link to successful Jenkins build. > > > >

Re: [VOTE] 2.7.0 RC5

Hi Bill, Just a heads up that KAFKA-9393 that was previously marked as fixed in 2.7.0 has now been changed to 2.8.0. The corresponding PR is not present in 2.7.0 commit history. Please could you regenerate the release notes to help pick up this change? Cheers, Kowshik On Tue, Dec 15, 2020 at

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #315

See Changes: [github] KAFKA-10776: Add version attribute in RequestsPerSec metrics documentation (#9661) -- [...truncated 3.49 MB...]

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Hi Satish, Thanks for the updates! A few more comments below. 9001. Under the "Upgrade" section, there is a line mentioning: "Upgrade the existing Kafka cluster to 2.7 version and allow this to run for the log retention of user topics that you want to enable tiered storage. This will allow all

Re: [VOTE] 2.7.0 RC5

Thanks for voting John, I'm cc'ing the dev list as well. On Mon, Dec 14, 2020 at 8:35 PM John Roesler wrote: > Thanks for this release, Bill, > > I ran though the quickstart (just the zk, broker, and > console clients part), verified the signatures, and also > built and ran the tests. > > I'm

Jenkins build is back to normal : Kafka » kafka-trunk-jdk8 #290

See

Re: [VOTE] 2.7.0 RC5

All, I'm closing this vote in order to get this critical PR CVE-2020-25649: bumping jackson to patched version merged into 2.7. Once we merge the PR, I'll push out a new RC. Thanks to all who voted for this RC. Bill On Tue, Dec 15, 2020 at 1:16 PM

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hi, Colin, Thanks for the reply. A few more follow up comments. 210. initial.broker.registration.timeout.ms: The default value is 90sec, which seems long. If a broker fails the registration because of incorrect configs, we want to fail faster. In comparison, the defaults for

[jira] [Resolved] (KAFKA-10855) Non-local return in envelope validation in causes unexpected response send

[ https://issues.apache.org/jira/browse/KAFKA-10855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-10855. - Resolution: Fixed > Non-local return in envelope validation in causes unexpected

[jira] [Resolved] (KAFKA-10839) Improve consumer group coordinator unavailable message

[ https://issues.apache.org/jira/browse/KAFKA-10839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-10839. - Fix Version/s: 2.8.0 Resolution: Fixed > Improve consumer group coordinator

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #336

See Changes: [github] KAFKA-10854: fix flaky testConnectionRatePerIp test (#9752) [github] KAFKA-10776: Add version attribute in RequestsPerSec metrics documentation (#9661) [github] KAFKA-6084:

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #335

See Changes: [github] KAFKA-10525: Emit JSONs with new auto-generated schema (KIP-673) (#9526) -- [...truncated 6.99 MB...]

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #313

See Changes: [github] KAFKA-10852: AlterIsr should not be throttled (#9747) -- [...truncated 6.99 MB...]

[jira] [Created] (KAFKA-10858) Convert connect protocol header schemas to use generated protocol

dengziming created KAFKA-10858: -- Summary: Convert connect protocol header schemas to use generated protocol Key: KAFKA-10858 URL: https://issues.apache.org/jira/browse/KAFKA-10858 Project: Kafka

Jenkins build is back to normal : Kafka » kafka-trunk-jdk15 #337

See

Jenkins build is back to normal : Kafka » kafka-trunk-jdk11 #316

See

Re: Improving crash-restart catchup speed

Hi. One possible solution I can imagine is to use replication throttle. https://cwiki.apache.org/confluence/display/KAFKA/KIP-73+Replication+Quotas You can set lower replication quota for other brokers -> failed broker traffic during catching-up to prevent exhausting storage throughput.

Jenkins build is back to normal : Kafka » kafka-2.7-jdk8 #80

See

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #317

See Changes: [github] KAFKA-10417: Update Cogrouped processor to work with suppress() and joins (#9727) [github] KAFKA-10855; Fix non-local return in `KafkaApis.handle` (#9753) [github]

Build failed in Jenkins: Kafka » kafka-2.6-jdk8 #63

See Changes: [Ismael Juma] MINOR: Update jackson databind to 2.10.5.1 (#9702) -- [...truncated 3.17 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #334

See Changes: [github] KAFKA-10852: AlterIsr should not be throttled (#9747) -- [...truncated 3.50 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #79

See Changes: [Ismael Juma] KAFKA-10852: AlterIsr should not be throttled (#9747) -- [...truncated 3.44 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: Kafka » kafka-2.5-jdk8 #26

See Changes: [Ismael Juma] MINOR: Update jackson databind to 2.10.5.1 (#9702) -- [...truncated 3.10 MB...]