Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #1632

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #1631

See Changes: -- [...truncated 537266 lines...] [2023-03-01T04:54:39.150Z] > Task :clients:compileTestJava UP-TO-DATE [2023-03-01T04:54:39.150Z] > Task :clients:testClasses

[jira] [Resolved] (KAFKA-14371) quorum-state file contains empty/unused clusterId field

[ https://issues.apache.org/jira/browse/KAFKA-14371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-14371. --- Fix Version/s: 3.5.0 Resolution: Fixed > quorum-state file contains empty/unused clusterId

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1630

See

[jira] [Resolved] (KAFKA-12639) AbstractCoordinator ignores backoff timeout when joining the consumer group

[ https://issues.apache.org/jira/browse/KAFKA-12639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-12639. --- Fix Version/s: 3.5.0 Resolution: Fixed > AbstractCoordinator ignores backoff timeout

Re: [VOTE] KIP-903: Replicas with stale broker epoch should not be allowed to join the ISR

Thanks Calvin, +1 from me. On Mon, Feb 27, 2023 at 9:41 AM Calvin Liu wrote: > Hi Jason, > Updated the fields accordingly. Also, rename the BrokerState to > ReplicaState. > Thanks. > > On Wed, Feb 22, 2023 at 4:38 PM Jason Gustafson > > wrote: > > > Hi Calvin, > > > > The `BrokerState` struct

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #1629

See

Re: [DISCUSS] KIP-909: Allow clients to rebootstrap DNS lookup failure

Hi Philip, > Having an overall timeout also seems reasonable, but I wonder what should the client do after running out of the time? Should we throw a non-retriable exception (instead of TimeoutExceptoin to stop the client from retrying) and alert the user to examine the config and the DNS server?

[jira] [Resolved] (KAFKA-14769) NPE in ControllerMetricsManager when upgrading from old KRaft version

[ https://issues.apache.org/jira/browse/KAFKA-14769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-14769. -- Resolution: Invalid > NPE in ControllerMetricsManager when upgrading from old KRaft version >

[jira] [Created] (KAFKA-14769) NPE in ControllerMetricsManager when upgrading from old KRaft version

David Arthur created KAFKA-14769: Summary: NPE in ControllerMetricsManager when upgrading from old KRaft version Key: KAFKA-14769 URL: https://issues.apache.org/jira/browse/KAFKA-14769 Project: Kafka

Re: [VOTE] KIP-900: KRaft kafka-storage.sh API additions to support SCRAM for Kafka Brokers

Hi all, I am going to close the vote and start implementing. The KIP is accepted with three binding votes from Colin, Jose, and Manikumar. --Proven On Sat, Feb 25, 2023 at 1:21 AM Manikumar wrote: > +1 (binding) > > Thanks for the KIP. > > On Wed, Feb 22, 2023 at 3:48 AM José Armando García

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #1628

See Changes: -- [...truncated 448217 lines...] [2023-02-28T20:04:32.224Z] [2023-02-28T20:04:32.224Z] Gradle Test Run :core:integrationTest > Gradle Test Executor 173 >

Re: [DISCUSS] KIP-909: Allow clients to rebootstrap DNS lookup failure

Jason: Thanks for the feedback. Now giving it a second thought, I think your suggestion of logging the error might make sense, as I could imagine most users would just continue to retry, so it might not be necessary to throw an exception anyway. Having an overall timeout also seems reasonable,

Re: [DISCUSS] KIP-909: Allow clients to rebootstrap DNS lookup failure

One more random thought I had just as I pushed send. We're currently treating this problem somewhat narrowly by focusing only on the DNS resolution of the bootstrap servers. Even if the servers resolve, there's no guarantee that they are reachable by the client. Would it make sense to have a

Re: [DISCUSS] KIP-909: Allow clients to rebootstrap DNS lookup failure

Hi Philip, An alternative is not to fail at all. Every other network error is caught and handled internally in the client. We see this case as different because a DNS resolution error may imply misconfiguration. Could it also imply that the DNS server is unavailable? I'm not sure why that case

Creating a JIRA account

Hi, due to documentation as a new contributor, I should create a JIRA account and assign a ticket I want to work on to me. But recently new JIRA account creation was disabled. What should I do? Should I work with a ticket without assigning it to me (with a risk of work duplication)? Or should I

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.4 #92

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.3 #159

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1627

See

Fwd: Request for Jira Account Creation

Hi Team, Just following up for the JIRA user creation. Regards Ganesh -- Forwarded message - From: Ganesh S Date: Fri, Feb 24, 2023 at 10:53 AM Subject: Request for Jira Account Creation To: Dear Team, I am writing to request a Jira account for the purpose of contributing

Re: [DISCUSS] KIP-909: Allow clients to rebootstrap DNS lookup failure

Hi Philip, Yeah, it's basically DNS resolution we're talking about, though there's some additional subtlety there with the logic introduced by KIP-235 [1]. Essentially it should cover any scenario that causes a client constructor to fail with the current logic but would not after this KIP is

Re: [VOTE] KIP-898: Modernize Connect plugin discovery

Thanks for the well-detailed KIP, Greg. It'll be a needed improvement. +1(binding) Thanks, Bill On Tue, Feb 28, 2023 at 9:51 AM John Roesler wrote: > Thanks for the KIP, Greg! > > I’m +1 (binding) > > I really appreciate all the care you took in the migration and test > design. > > Thanks, >

Re: [VOTE] KIP-898: Modernize Connect plugin discovery

Thanks for the KIP, Greg! I’m +1 (binding) I really appreciate all the care you took in the migration and test design. Thanks, John On Tue, Feb 28, 2023, at 04:33, Federico Valeri wrote: > +1 (non binding) > > Thanks > Fede > > On Tue, Feb 28, 2023 at 10:10 AM Mickael Maison > wrote: >> >>

[jira] [Resolved] (KAFKA-14659) source-record-write-[rate|total] metrics include filtered records

[ https://issues.apache.org/jira/browse/KAFKA-14659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-14659. --- Resolution: Fixed > source-record-write-[rate|total] metrics include filtered records >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1626

See

Re: [VOTE] KIP-898: Modernize Connect plugin discovery

+1 (non binding) Thanks Fede On Tue, Feb 28, 2023 at 10:10 AM Mickael Maison wrote: > > +1 (binding) > > Thanks, > Mickael > > On Mon, Feb 27, 2023 at 7:42 PM Chris Egerton wrote: > > > > +1 (binding). Thanks for the KIP! > > > > On Mon, Feb 27, 2023 at 12:51 PM Greg Harris > > wrote: > > > >

Re: [VOTE] KIP-898: Modernize Connect plugin discovery

+1 (binding) Thanks, Mickael On Mon, Feb 27, 2023 at 7:42 PM Chris Egerton wrote: > > +1 (binding). Thanks for the KIP! > > On Mon, Feb 27, 2023 at 12:51 PM Greg Harris > wrote: > > > Hi, > > > > I'd like to call a vote for KIP-898 which aims to improve the performance > > of Connect startup

[jira] [Resolved] (KAFKA-13771) Support to explicitly delete delegationTokens that have expired but have not been automatically cleaned up

[ https://issues.apache.org/jira/browse/KAFKA-13771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RivenSun resolved KAFKA-13771. -- Resolution: Resolved > Support to explicitly delete delegationTokens that have expired but have not