Jenkins build is back to normal : Kafka » kafka-2.6-jdk8 #107

See

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

See Changes: [github] KAFKA-12500: fix memory leak in thread cache (#10355) -- [...truncated 3.69 MB...] AuthorizerIntegrationTest >

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

See Changes: [github] HOTFIX: fix build in EmitOnChangeIntegrationTest (#10364) -- [...truncated 3.45 MB...]

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

See Changes: [github] KAFKA-12500: fix memory leak in thread cache (#10355) -- [...truncated 7.35 MB...] UserClientIdQuotaTest >

Build failed in Jenkins: Kafka » kafka-2.8-jdk8 #75

See Changes: [A. Sophie Blee-Goldman] KAFKA-12500: fix memory leak in thread cache (#10355) -- [...truncated 3.60 MB...] PasswordEncoderTest >

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

See Changes: [github] MINOR: Use self-managed mode instead of KIP-500 and nozk (#10362) -- [...truncated 7.38 MB...] AclAuthorizerTest >

Jenkins build is back to normal : Kafka » kafka-2.8-jdk8 #74

See

Re: [kafka-clients] [VOTE] 2.7.1 RC0

Fix has been merged, the 2.7 release should be unblocked. Thanks! On Fri, Mar 19, 2021 at 4:11 PM Sophie Blee-Goldman wrote: > Ah I think the test from that PR broke the 2.7 branch, I was looking at > the wrong tests when I pushed and > noticed the 2.7 test had failed to compile just now. I'll

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

See Changes: [A. Sophie Blee-Goldman] KAFKA-12508: Emit records with same value and same timestamp (#10360) -- [...truncated 3.18 MB...]

Re: [VOTE] 2.6.2 RC0

Hi, I was taking a look at this release candidate and noticed a number of things from a licensing compliance point of view the set a little odd. Now there may be some history here that I'm unaware of and a good reason why things are like this. I can see: - The LICENSE files include things

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

See Changes: [github] KAFKA-12508: Emit records with same value and same timestamp (#10360) [github] MINOR: Use self-managed mode instead of KIP-500 and nozk (#10362)

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

See Changes: [A. Sophie Blee-Goldman] KAFKA-12508: Emit records with same value and same timestamp (#10360) -- [...truncated 2.37 MB...]

[jira] [Resolved] (KAFKA-10821) Send cluster id information with the FetchSnapshot request

[ https://issues.apache.org/jira/browse/KAFKA-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dengziming resolved KAFKA-10821. Resolution: Duplicate > Send cluster id information with the FetchSnapshot request >

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

See Changes: [github] MINOR: Assume unclean shutdown for metadata log (#10363) -- [...truncated 3.68 MB...] LogValidatorTest >

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

See Changes: [github] MINOR: Assume unclean shutdown for metadata log (#10363) [github] KAFKA-12508: Emit records with same value and same timestamp (#10360)

Build failed in Jenkins: Kafka » kafka-2.8-jdk8 #73

See Changes: [Jason Gustafson] MINOR: Assume unclean shutdown for metadata log (#10363) -- [...truncated 3.62 MB...] BrokerEndPointTest > testFromJsonV1()

Re: [kafka-clients] [VOTE] 2.7.1 RC0

Ah I think the test from that PR broke the 2.7 branch, I was looking at the wrong tests when I pushed and noticed the 2.7 test had failed to compile just now. I'll open a quick PR to fix -- sorry about that On Fri, Mar 19, 2021 at 3:53 PM Sophie Blee-Goldman wrote: > Hey Mickael, I just merged

Re: [kafka-clients] [VOTE] 2.7.1 RC0

Hey Mickael, I just merged the fix back to 2.7 so you should be good to go Thanks for the PR Bruno! On Fri, Mar 19, 2021 at 9:34 AM Mickael Maison wrote: > Thanks Bruno, > > That indeed sounds like a blocker. > > I'm closing this vote, I'll build a new RC once a fix is merged into 2.7 > > On

Re: [kafka-clients] [VOTE] 2.6.2 RC0

Thanks Bruno. I agree this qualifies as a blocker since it was a regression in 2.6 and may result in data loss. I'll roll a new RC with the fix On Fri, Mar 19, 2021 at 7:03 AM 'Bruno Cadonna' via kafka-clients < kafka-clie...@googlegroups.com> wrote: > Hi Sophie, > > Correction to my last

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

See Changes: [github] KAFKA-9189: Use MetadataCache instead of ZK during controlled shutdown to avoid hang (#10361) [github] KAFKA-12318: system tests need to fetch Topic IDs via Admin Client

Build failed in Jenkins: Kafka » kafka-2.8-jdk8 #72

See Changes: [Colin McCabe] MINOR: The new KIP-500 code should treat cluster ID as a string (#10357) -- [...truncated 7.26 MB...] KafkaZkClientTest >

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

See Changes: [github] KAFKA-12318: system tests need to fetch Topic IDs via Admin Client instead of via ZooKeeper (#10286) -- [...truncated 3.69 MB...]

Re: [DISCUSS] KIP-723: Add socket.tcp.no.delay property to Kafka Config

Hi David, Thanks for your comment. Client connections are insignificant on my test cluster. But I can add this setting just in case. Best regards, Andrei > On 19 Mar 2021, at 23:19, David Jacot wrote: > > Hi Andrei, > > Thanks for the KIP. > > Should we consider adding the setting in the

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

See Changes: [github] KAFKA-12440; ClusterId validation for Vote, BeginQuorum, EndQuorum and FetchSnapshot (#10289) [github] KAFKA-9189: Use MetadataCache instead of ZK during controlled shutdown

Re: [DISCUSS] KIP-723: Add socket.tcp.no.delay property to Kafka Config

Hi Andrei, Thanks for the KIP. Should we consider adding the setting in the clients as well? I think that it is also enabled by default in the clients. Could it be useful? Best, David Le ven. 19 mars 2021 à 13:41, Ismael Juma a écrit : > Hi Andrei, > > I would start the vote on Monday if

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

See Changes: [github] MINOR: The new KIP-500 code should treat cluster ID as a string (#10357) [github] KAFKA-12253: Add tests that cover all of the cases for ReplicatedLog's

[jira] [Resolved] (KAFKA-12318) system tests need to fetch Topic IDs via Admin Client instead of via ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-12318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-12318. Resolution: Fixed > system tests need to fetch Topic IDs via Admin Client instead of via

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

See Changes: [github] MINOR: Remove inexistent parameter in doc of `LogManager#getOrCreateLog` (#10359) [github] MINOR: The new KIP-500 code should treat cluster ID as a string (#10357) [github]

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

See Changes: [github] MINOR: Remove inexistent parameter in doc of `LogManager#getOrCreateLog` (#10359) [github] MINOR: The new KIP-500 code should treat cluster ID as a string (#10357) [github]

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

See Changes: [github] MINOR: Remove inexistent parameter in doc of `LogManager#getOrCreateLog` (#10359) -- [...truncated 3.69 MB...]

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

See Changes: [github] KAFKA-10070: parameterize Connect unit tests to remove code duplication (#10299) -- [...truncated 7.38 MB...] KafkaZkClientTest >

[jira] [Resolved] (KAFKA-12440) ClusterId validation for Vote, BeginQourum and EndQuorum

[ https://issues.apache.org/jira/browse/KAFKA-12440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-12440. - Resolution: Fixed > ClusterId validation for Vote, BeginQourum and EndQuorum >

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

See

Re: [ANNOUNCE] New committer: Tom Bentley

Congratulations, Tom! Randall On Fri, Mar 19, 2021 at 11:33 AM Colin McCabe wrote: > Congratulations, Tom! > > Colin > > On Fri, Mar 19, 2021, at 08:09, Viktor Somogyi-Vass wrote: > > Congrats Tom! :) > > > > On Wed, Mar 17, 2021 at 3:47 PM Chia-Ping Tsai > wrote: > > > > > Congratulations!!!

Re: [ANNOUNCE] New Kafka PMC Member: Chia-Ping Tsai

Congratulations, Chia-Ping! Randall On Thu, Mar 18, 2021 at 5:57 AM Satish Duggana wrote: > Congratulations Chia-Ping! > > On Thu, 18 Mar 2021 at 10:18, Kowshik Prakasam > wrote: > > > Congrats Chia-Ping! > > > > On Tue, Mar 16, 2021, 6:16 PM Dongjin Lee wrote: > > > > > > > > > > >

Re: [DISCUSS] KIP-707: The future of KafkaFuture

My two cents: keep the same method and class names and just use a different package. Strongly dislike coming up with slightly different names for everything. Ryanne On Tue, Feb 2, 2021, 4:41 AM Tom Bentley wrote: > I've previously discounted the possibility of an "Admin2" client, but > seeing

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

See Changes: [github] KAFKA-10070: parameterize Connect unit tests to remove code duplication (#10299) -- [...truncated 3.69 MB...] UserQuotaTest >

Re: [kafka-clients] [VOTE] 2.7.1 RC0

Thanks Bruno, That indeed sounds like a blocker. I'm closing this vote, I'll build a new RC once a fix is merged into 2.7 On Fri, Mar 19, 2021 at 2:04 PM Bruno Cadonna wrote: > > Hi Mickael, > > Correction to my last e-mail: The bug does not break eos, but it breaks > at-least-once. > > Bruno

Re: [ANNOUNCE] New committer: Tom Bentley

Congratulations, Tom! Colin On Fri, Mar 19, 2021, at 08:09, Viktor Somogyi-Vass wrote: > Congrats Tom! :) > > On Wed, Mar 17, 2021 at 3:47 PM Chia-Ping Tsai wrote: > > > Congratulations!!! > > > > On 2021/03/15 17:59:56, Mickael Maison wrote: > > > Hi all, > > > > > > The PMC for Apache

Re: [DISCUSS] Apache Kafka 2.8.0 release

Hello John, We merged the fix for the blocker I mentioned earlier https://issues.apache.org/jira/browse/KAFKA-12462 https://github.com/apache/kafka/pull/10311 best walker On Fri, Mar 19, 2021 at 7:09 AM Bruno Cadonna wrote: > Hi John, > > Correction to my last e-mail: The bug does not break

Re: [DISCUSS] KIP-707: The future of KafkaFuture

Hi Tom, I think it makes sense to go with the incremental option. I don't like CompletableFuture because it exposes a bunch of unsafe methods. Since we're adding this to `KafkaFuture`, then methods like `get` are already available. What benefit is there for exposing `CompletableFuture` instead of

Re: [ANNOUNCE] New committer: Tom Bentley

Congrats Tom! :) On Wed, Mar 17, 2021 at 3:47 PM Chia-Ping Tsai wrote: > Congratulations!!! > > On 2021/03/15 17:59:56, Mickael Maison wrote: > > Hi all, > > > > The PMC for Apache Kafka has invited Tom Bentley as a committer, and > > we are excited to announce that he accepted! > > > > Tom

Re: [DISCUSS] KIP-707: The future of KafkaFuture

Hi Tom, Have you considered to directly subclass CompletableFuture? Can we do this? Maybe a good addition to the alternatives. Thanks, Viktor On Wed, Feb 24, 2021 at 10:13 AM Tom Bentley wrote: > If the next release is going to be Kafka 3.0, as seems to be the case, it > would be a great time

[jira] [Created] (KAFKA-12512) Pass client listener and security protocol to KafkaClusterTestKey

David Arthur created KAFKA-12512: Summary: Pass client listener and security protocol to KafkaClusterTestKey Key: KAFKA-12512 URL: https://issues.apache.org/jira/browse/KAFKA-12512 Project: Kafka

[jira] [Resolved] (KAFKA-10070) Parameterize Connect unit tests to remove code duplication

[ https://issues.apache.org/jira/browse/KAFKA-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-10070. Fix Version/s: 3.0.0 Assignee: Lev Zemlyanov (was: Konstantine Karantasis)

Re: [kafka-clients] [VOTE] 2.7.1 RC0

Hi Mickael, Correction to my last e-mail: The bug does not break eos, but it breaks at-least-once. Bruno On 19.03.21 14:54, Bruno Cadonna wrote: Hi Mickael, Please have a look at the following bug report: https://issues.apache.org/jira/browse/KAFKA-12508 I set its priority to blocker

Re: [kafka-clients] [VOTE] 2.6.2 RC0

Hi Sophie, Correction to my last e-mail: The bug does not break eos, but it breaks at-least-once. Bruno On 19.03.21 14:54, Bruno Cadonna wrote: Hi Sophie, Please have a look at the following bug report: https://issues.apache.org/jira/browse/KAFKA-12508 I set its priority to blocker since

Re: [DISCUSS] Apache Kafka 2.8.0 release

Hi John, Correction to my last e-mail: The bug does not break eos, but it breaks at-least-once. Bruno On 19.03.21 14:55, Bruno Cadonna wrote: Hi John, Please have a look at the following bug report: https://issues.apache.org/jira/browse/KAFKA-12508 I set its priority to blocker since

Re: [DISCUSS] Apache Kafka 2.8.0 release

Hi John, Please have a look at the following bug report: https://issues.apache.org/jira/browse/KAFKA-12508 I set its priority to blocker since the bug might break at-least-once and exactly-once processing guarantees. Feel free to set it back to major, if you think that it is not a blocker.

Re: [kafka-clients] [VOTE] 2.7.1 RC0

Hi Mickael, Please have a look at the following bug report: https://issues.apache.org/jira/browse/KAFKA-12508 I set its priority to blocker since the bug might break at-least-once and exactly-once processing guarantees. Feel free to set it back to major, if you think that it is not a

Re: [kafka-clients] [VOTE] 2.6.2 RC0

Hi Sophie, Please have a look at the following bug report: https://issues.apache.org/jira/browse/KAFKA-12508 I set its priority to blocker since the bug might break at-least-once and exactly-once processing guarantees. Feel free to set it back to major, if you think that it is not a

[jira] [Created] (KAFKA-12511) Flaky test DynamicConnectionQuotaTest.testDynamicListenerConnectionCreationRateQuota()

dengziming created KAFKA-12511: -- Summary: Flaky test DynamicConnectionQuotaTest.testDynamicListenerConnectionCreationRateQuota() Key: KAFKA-12511 URL: https://issues.apache.org/jira/browse/KAFKA-12511

Re: [DISCUSS] KIP-723: Add socket.tcp.no.delay property to Kafka Config

Hi Andrei, I would start the vote on Monday if there are no comments. Ismael On Fri, Mar 19, 2021 at 5:36 AM Andrei Iatsuk wrote: > No comments yet. I don’t know this is good or not. May I start voting? > > > On 17 Mar 2021, at 18:32, Andrei Iatsuk wrote: > > > > Hello everyone, > > > > I

Re: [DISCUSS] KIP-723: Add socket.tcp.no.delay property to Kafka Config

No comments yet. I don’t know this is good or not. May I start voting? > On 17 Mar 2021, at 18:32, Andrei Iatsuk wrote: > > Hello everyone, > > I would like to start a discussion on KIP-723, which propose adding a Kafka > Config property with TCP_NODELAY socket option flag, that currently

[jira] [Created] (KAFKA-12510) Unable to access Kafka connection on a machine behind the company fireall

satyaveni created KAFKA-12510: - Summary: Unable to access Kafka connection on a machine behind the company fireall Key: KAFKA-12510 URL: https://issues.apache.org/jira/browse/KAFKA-12510 Project: Kafka

[jira] [Resolved] (KAFKA-10160) Kafka MM2 consumer configuration

[ https://issues.apache.org/jira/browse/KAFKA-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-10160. Fix Version/s: 2.8.0 Resolution: Fixed > Kafka MM2 consumer configuration >

Re: [VOTE] 2.7.1 RC0

+1 On Fri, Mar 19, 2021 at 4:56 PM Mickael Maison wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of Apache Kafka 2.7.1. > > Apache Kafka 2.7.1 is a bugfix release and 40 issues have been fixed > since 2.7.0. > > Release notes for the

[VOTE] 2.7.1 RC0

Hello Kafka users, developers and client-developers, This is the first candidate for release of Apache Kafka 2.7.1. Apache Kafka 2.7.1 is a bugfix release and 40 issues have been fixed since 2.7.0. Release notes for the 2.7.1 release:

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

See Changes: [github] KAFKA-12503: inform threads to resize their cache instead of doing so for them (#10356) -- [...truncated 7.38 MB...]

[jira] [Created] (KAFKA-12509) Tighten up StateDirectory thread locking

A. Sophie Blee-Goldman created KAFKA-12509: -- Summary: Tighten up StateDirectory thread locking Key: KAFKA-12509 URL: https://issues.apache.org/jira/browse/KAFKA-12509 Project: Kafka