[jira] [Resolved] (KAFKA-13294) Upgrade Netty to 4.1.68 for CVE fixes

[ https://issues.apache.org/jira/browse/KAFKA-13294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjin Lee resolved KAFKA-13294. - Resolution: Fixed [~mimaison] Here it is. > Upgrade Netty to 4.1.68 for CVE fixes >

Re: New Kafka Consumer : unknown member id

Hi, Which version of kafka client are you using? I can't find this error message in the source code. When googling this error message, it showed the error is in Kafka v0.9. Could you try to use the V3.0.0 and see if that issue still exist? Thank you. Luke On Thu, Oct 28, 2021 at 11:15 PM Kafka

[jira] [Created] (KAFKA-13418) Brokers disconnect intermittently with TLS1.3

shylaja kokoori created KAFKA-13418: --- Summary: Brokers disconnect intermittently with TLS1.3 Key: KAFKA-13418 URL: https://issues.apache.org/jira/browse/KAFKA-13418 Project: Kafka Issue

[jira] [Resolved] (KAFKA-13118) Backport KAFKA-9887 to 3.0 branch after 3.0.0 release

[ https://issues.apache.org/jira/browse/KAFKA-13118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-13118. --- Resolution: Fixed Backported to the `3.0` branch. Will be in the 3.0.1 release. > Backport

[jira] [Created] (KAFKA-13417) Dynamic thread pool re-configurations may not get processed

Jason Gustafson created KAFKA-13417: --- Summary: Dynamic thread pool re-configurations may not get processed Key: KAFKA-13417 URL: https://issues.apache.org/jira/browse/KAFKA-13417 Project: Kafka

[jira] [Resolved] (KAFKA-13202) KIP-768: Extend SASL/OAUTHBEARER with Support for OIDC

[ https://issues.apache.org/jira/browse/KAFKA-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13202. - Fix Version/s: 3.1.0 Resolution: Fixed merged the PR to trunk. > KIP-768: Extend

Re: [DISCUSS] Apache Kafka 3.1.0 release

Hi David, I've moved KIP-618 to the "postponed" section as it will not be merged in time due to lack of review. Cheers, Chris On Thu, Oct 28, 2021 at 1:07 PM David Jacot wrote: > Hi team, > > Just a quick reminder that the Feature freeze is tomorrow (October 29th). > In order to be fair with

Re: [DISCUSS] Apache Kafka 3.1.0 release

Hi team, Just a quick reminder that the Feature freeze is tomorrow (October 29th). In order to be fair with everyone in all the time zones, I plan to cut the release branch early next week. Cheers, David On Mon, Oct 18, 2021 at 9:56 AM David Jacot wrote: > Hi team, > > KIP freeze for the next

Re: [DISCUSS] KIP-768: Extend SASL/OAUTHBEARER with Support for OIDC

Hi all, I just wanted to mention that there have been some minor updates to the configuration for OAuth. The most relevant change is that I introduced an exponential backoff for when we attempt to retrieve the JWKS (JSON Web Key Set) from the OAuth/OIDC provider. Rather than hard-code the

New Kafka Consumer : unknown member id

Dear Kafka Experts We have set up a group.id (consumer ) = YYY But when tried to connect to kafka instance : i get this error message. I am sure this consumer (group id does not exist in kafka) .We user plain text protocol to connect to kafka 2.8.0. Please suggest how to resolve this issue.

[jira] [Created] (KAFKA-13416) Add topic ids to any metrics that has topic and partition tags

Omnia Ibrahim created KAFKA-13416: - Summary: Add topic ids to any metrics that has topic and partition tags Key: KAFKA-13416 URL: https://issues.apache.org/jira/browse/KAFKA-13416 Project: Kafka

Re: [DISCUSS] KIP-779: Allow Source Tasks to Handle Producer Exceptions

Yes, that makes sense. And it fits in very nicely with the current error handling framework. On Thu, Oct 28, 2021 at 10:39 AM Knowles Atchison Jr wrote: > That would work. I originally thought that it would be confusing to > overload that function when a Record that wasn't actually written, but

Re: [DISCUSS] KIP-779: Allow Source Tasks to Handle Producer Exceptions

That would work. I originally thought that it would be confusing to overload that function when a Record that wasn't actually written, but looking at SourceTask more closely, in commitRecord(SourceRecord, RecordMetadata), the RecordMetadata is set to null in the event of a filtered transformation

[jira] [Created] (KAFKA-13415) Track topic deletion state without ZK

Omnia Ibrahim created KAFKA-13415: - Summary: Track topic deletion state without ZK Key: KAFKA-13415 URL: https://issues.apache.org/jira/browse/KAFKA-13415 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-779: Allow Source Tasks to Handle Producer Exceptions

To ack the message back to the source system, we already have a commitRecord method. Once the bad record is handled by skip/dlq, we could just call commitRecord() on it? On Thu, Oct 28, 2021 at 9:35 AM Knowles Atchison Jr wrote: > Hi Chris, > > Thank you for your reply! > > It is a clarity

Track topic deletion state without ZK

Hi, Kafka topicCommand used to report which topic is marked for deletion by checking the znode on zookeeper; this feature has been deprecated without replacement as part of KAFKA-12596 Remove deprecated --zookeeper in topicCommands . Also as far

Re: [DISCUSS] KIP-779: Allow Source Tasks to Handle Producer Exceptions

Hi Chris, Thank you for your reply! It is a clarity error regarding the javadoc. I am not operationally familiar with all of the exceptions Kafka considers non-retriable, so I pulled the list from Callback.java:

[jira] [Created] (KAFKA-13414) Remove Powermock from connect.storage package

Mickael Maison created KAFKA-13414: -- Summary: Remove Powermock from connect.storage package Key: KAFKA-13414 URL: https://issues.apache.org/jira/browse/KAFKA-13414 Project: Kafka Issue

Re: Request for permission to assign JIRA ticket (KAFKA-13403) to myself

Hi Arun, I granted you permissions. Thanks On Thu, Oct 28, 2021 at 1:01 PM Arun Mathew wrote: > > Ah! It is arunmathew88. > Thank you. > -- > With Regards, > Arun Mathew > > On Thu, Oct 28, 2021 at 2:28 PM Matthias J. Sax wrote: > > > What is you user name? > > > > On 10/27/21 6:08 PM, Arun

Re: Request for permission to assign JIRA ticket (KAFKA-13403) to myself

Ah! It is arunmathew88. Thank you. -- With Regards, Arun Mathew On Thu, Oct 28, 2021 at 2:28 PM Matthias J. Sax wrote: > What is you user name? > > On 10/27/21 6:08 PM, Arun Mathew wrote: > > Hi, > > Please give me the relevant permissions to take up tickets. > > -- > > With Regards, > >

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

See Changes: -- [...truncated 495902 lines...] [2021-10-28T09:05:06.737Z] [2021-10-28T09:05:06.737Z] PlaintextConsumerTest > testCommitMetadata() STARTED

[jira] [Resolved] (KAFKA-13413) Upgrade Netty to 4.1.68 for CVE fixes

[ https://issues.apache.org/jira/browse/KAFKA-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Mongelli resolved KAFKA-13413. Resolution: Abandoned Bad clone from KAFKA-13294 > Upgrade Netty to 4.1.68 for

[jira] [Created] (KAFKA-13413) Upgrade Netty to 4.1.68 for CVE fixes

Dominique Mongelli created KAFKA-13413: -- Summary: Upgrade Netty to 4.1.68 for CVE fixes Key: KAFKA-13413 URL: https://issues.apache.org/jira/browse/KAFKA-13413 Project: Kafka Issue

Re: [DISCUSS] KIP-779: Allow Source Tasks to Handle Producer Exceptions

Hi Knowles, Thanks for the KIP! Could you please call out some use-cases on what the source connectors would do when they hit such exceptions? I'm wondering if we would need to do anything other than skipping such records, writing some log messages, and/or writing some error context to a DLQ?