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

See

Re: Improve flaky test reporting (KAFKA-12216)

Hi David, I agree it'll be great if we could distinguish between "flakyFailure" and "alwaysFailure". And I also agree we should still show the "flakyFailure" tests because there could be some potential bugs there. Thanks for working on it. Luke On Tue, Feb 13, 2024 at 12:57 AM Ismael Juma

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

See

[jira] [Resolved] (KAFKA-9376) Plugin class loader not found using MM2

[ https://issues.apache.org/jira/browse/KAFKA-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-9376. Fix Version/s: 2.5.0 Resolution: Fixed > Plugin class loader not found using MM2 >

[jira] [Resolved] (KAFKA-7217) Loading dynamic topic data into kafka connector sink using regex

[ https://issues.apache.org/jira/browse/KAFKA-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-7217. Fix Version/s: 1.1.0 Resolution: Fixed > Loading dynamic topic data into kafka connector

[jira] [Created] (KAFKA-16245) DescribeConsumerGroupTest failing

Justine Olshan created KAFKA-16245: -- Summary: DescribeConsumerGroupTest failing Key: KAFKA-16245 URL: https://issues.apache.org/jira/browse/KAFKA-16245 Project: Kafka Issue Type: Task

[jira] [Resolved] (KAFKA-6340) Support of transactions in KafkaConnect

[ https://issues.apache.org/jira/browse/KAFKA-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-6340. Fix Version/s: 3.3.0 Resolution: Fixed > Support of transactions in KafkaConnect >

[jira] [Resolved] (KAFKA-4961) Mirrormaker crash with org.apache.kafka.common.protocol.types.SchemaException

[ https://issues.apache.org/jira/browse/KAFKA-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-4961. Resolution: Won't Fix > Mirrormaker crash with

[jira] [Resolved] (KAFKA-3213) [CONNECT] It looks like we are not backing off properly when reconfiguring tasks

[ https://issues.apache.org/jira/browse/KAFKA-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-3213. Fix Version/s: 3.5.0 Resolution: Fixed > [CONNECT] It looks like we are not backing off

[jira] [Resolved] (KAFKA-16229) Slow expiration of Producer IDs leading to high CPU usage

[ https://issues.apache.org/jira/browse/KAFKA-16229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-16229. Resolution: Fixed > Slow expiration of Producer IDs leading to high CPU usage >

[jira] [Resolved] (KAFKA-13338) kafka upgrade 6.1.1 asking to change log.cleanup.policy from delete to compact

[ https://issues.apache.org/jira/browse/KAFKA-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-13338. - Resolution: Invalid > kafka upgrade 6.1.1 asking to change log.cleanup.policy from delete to

[jira] [Resolved] (KAFKA-13163) MySQL Sink Connector - JsonConverter - DataException: Unknown schema type: null

[ https://issues.apache.org/jira/browse/KAFKA-13163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-13163. - Resolution: Invalid > MySQL Sink Connector - JsonConverter - DataException: Unknown schema

Re: [VOTE] 3.7.0 RC4

+1 (non-binding). I used the staged binaries with Scala 2.13 and the staged Maven artifacts to run my tests. All seems to work fine. Thanks. Jakub On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate

Re: [DISCUSS] KIP-956: Tiered Storage Quotas

Comments inline On Wed, Dec 6, 2023 at 1:12 AM Jun Rao wrote: > Hi, Abhijeet, > > Thanks for the KIP. A few comments. > > 10. remote.log.manager.write.quota.default: > 10.1 For other configs, we > use replica.alter.log.dirs.io.max.bytes.per.second. To be consistent, > perhaps this can be sth

Re: [DISCUSS] KIP-956: Tiered Storage Quotas

Comments inline On Tue, Nov 28, 2023 at 3:50 PM Luke Chen wrote: > > Hi Abhijeet, > > Thanks for the KIP! > This is an important feature for tiered storage. > > Some comments: > 1. Will we introduce new metrics for this tiered storage quotas? > This is important because the admin can know the

Re: [PR] 3.7: Add blog post for Kafka 3.7 [kafka-site]

OmniaGM commented on code in PR #578: URL: https://github.com/apache/kafka-site/pull/578#discussion_r1486622896 ## blog.html: ## @@ -22,6 +22,119 @@ Blog + + + +Apache Kafka

Re: [PR] MINIOR: Mark JBOD as an early release [kafka-site]

OmniaGM commented on PR #579: URL: https://github.com/apache/kafka-site/pull/579#issuecomment-1939334651 @stanislavkozlovski can you have a look into this please? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[PR] MINIOR: Mark JBOD as an early release [kafka-site]

OmniaGM opened a new pull request, #579: URL: https://github.com/apache/kafka-site/pull/579 Update the blog to mark JBOD as early access -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [PR] 3.7: Add blog post for Kafka 3.7 [kafka-site]

OmniaGM commented on code in PR #578: URL: https://github.com/apache/kafka-site/pull/578#discussion_r1486615067 ## blog.html: ## @@ -22,6 +22,119 @@ Blog + + + +Apache Kafka

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

See

Re: Improve flaky test reporting (KAFKA-12216)

Sounds good. I am supportive of this change. Ismael On Mon, Feb 12, 2024 at 7:43 AM David Jacot wrote: > Hi Bruno, > > Yes, you're right. Sorry for the typo. > > Hi Ismael, > > You're right. Jenkins does not support the flakyFailure element and > hence the information is not at all in the

Re: Improve flaky test reporting (KAFKA-12216)

Hi Bruno, Yes, you're right. Sorry for the typo. Hi Ismael, You're right. Jenkins does not support the flakyFailure element and hence the information is not at all in the Jenkins report. I am still experimenting with printing the flaky tests somewhere. I will update this thread if I get

Re: [VOTE] 3.7.0 RC4

Hi Stanislav, Thanks for running the release. It gets a +1 (non-binding) from me. I run the following steps to validate: - Compiled with Java 17 and Scala 2.13.12 - Run unit and integration tests - "LogDirFailureTest > testIOExceptionDuringLogRoll(String).quorum=kraft" failed[1] several times

Re: Improve flaky test reporting (KAFKA-12216)

Hi David, Your message didn't make this clear, but you are saying that Jenkins does _not_ support the flakyFailure element and hence this information will be completely missing from the Jenkins report. Have we considered including the flakyFailure information ourselves? I have seen that being

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.7 #94

See

Re: Improve flaky test reporting (KAFKA-12216)

Hi David, I guess you meant to say "This does not mean that we should NOT continue our effort to reduce the number of flaky tests." I totally agree with what you wrote. I am also +1 on considering all failures for unit tests. Best, Bruno On 2/12/24 9:11 AM, David Jacot wrote: Hi folks,

[jira] [Created] (KAFKA-16244) Move code style exceptions from suppressions.xml to the code

David Jacot created KAFKA-16244: --- Summary: Move code style exceptions from suppressions.xml to the code Key: KAFKA-16244 URL: https://issues.apache.org/jira/browse/KAFKA-16244 Project: Kafka

Re: Apache Kafka 3.7.0 Release

Stanislav this *doesn't* seem like a blocker to me given the complexity, > public API changes and Fair enough, since it only has been seen for very high partition counts. The PR in trunk is under active review, i will cherry-pick it for 3.7.1. >

Re: [DISCUSS] KIP-932: Queues for Kafka

Hi Chirag, Thanks for your question. 28. Good catch. Those options were omitted in error. I will update the KIP. Thanks, Andrew > On 12 Feb 2024, at 13:06, Chirag Wadhwa wrote: > > Hi Andrew, > > Thank you for the KIP, it is a great read ! I just have a small question. > > 28. I noticed that

Re: [DISCUSS] KIP-932: Queues for Kafka

Hi Andrew, Thank you for the KIP, it is a great read ! I just have a small question. 28. I noticed that the "*--state*" and "*--timeout*" options are not mentioned for the kafka-share-groups.sh tool. Was this omission intentional, or is it possibly an oversight in the KIP? Thanks, Chirag On

[jira] [Resolved] (KAFKA-16239) Clean up references to non-existent IntegrationTestHelper

[ https://issues.apache.org/jira/browse/KAFKA-16239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divij Vaidya resolved KAFKA-16239. -- Resolution: Fixed > Clean up references to non-existent IntegrationTestHelper >

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

See

Re: [DISCUSS] KIP-932: Queues for Kafka

Hi Jun Thanks for your comments. 10. For read-uncommitted isolation level, the consumer just reads all records. For read-committed isolation level, the share-partition leader does the filtering to enable correct skipping of aborted records. The consumers in a share group are not aware of the

[jira] [Resolved] (KAFKA-14041) Avoid the keyword var for a variable declaration in ConfigTransformer

[ https://issues.apache.org/jira/browse/KAFKA-14041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divij Vaidya resolved KAFKA-14041. -- Resolution: Fixed > Avoid the keyword var for a variable declaration in ConfigTransformer >

Re: [DISCUSS] Kafka-Streams-Scala for Scala 3

The additional load on the ASF's CI infrastructure may or may not be a problem, but either way I don't think it is to be addressed within the scope of this particular change. Best, Matthias Am Mo., 12. Feb. 2024 um 11:37 Uhr schrieb Josep Prat : > Hi Matthias, > If I understand it right (I'm

Re: [DISCUSS] Kafka-Streams-Scala for Scala 3

Hi Matthias, If I understand it right (I'm not an expert in CI infra), Kafka uses the ASF shared Jenkins, meaning this would potentially increase the time-to-built for the rest of the projects. Best, On Mon, Feb 12, 2024 at 11:30 AM Matthias Berndt < matthias.ber...@ttmzero.com> wrote: > Hey

Re: [DISCUSS] Kafka-Streams-Scala for Scala 3

Hey Josep, wouldn't it be possible to run this in a separate CI job that runs in parallel? Then it shouldn't take any longer than today – assuming enough CI resources are available. Best, Matthias Am Mo., 12. Feb. 2024 um 09:14 Uhr schrieb Josep Prat : > Hi Matthias, > > One of the problems of

Re: Apache Kafka 3.7.0 Release

Hey Divij, that is a good point regarding KIP-848. David, as the author of the KIP, would you be able to drive this? Similarly, would anybody be willing to drive such an EA Release Note for the JBOD feature? Mayank, this *doesn't* seem like a blocker to me given the complexity, public API

[jira] [Created] (KAFKA-16243) Idle kafka-console-consumer with new consumer group protocol preemptively leaves group

Andrew Schofield created KAFKA-16243: Summary: Idle kafka-console-consumer with new consumer group protocol preemptively leaves group Key: KAFKA-16243 URL: https://issues.apache.org/jira/browse/KAFKA-16243

[jira] [Resolved] (KAFKA-16220) KTableKTableForeignKeyInnerJoinCustomPartitionerIntegrationTest#shouldThrowIllegalArgumentExceptionWhenCustomPartionerReturnsMultiplePartitions is flaky

[ https://issues.apache.org/jira/browse/KAFKA-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucas Brutschy resolved KAFKA-16220. Resolution: Fixed >

Re: [DISCUSS] Kafka-Streams-Scala for Scala 3

Hi Matthias, One of the problems of adding support for Scala 3 for the scala-streams submodule is that we would need to have another build run on CI (which is already extremely long). I guess we could restrict this only when having changes on the Stream module(s). If I remember it correctly, when

Improve flaky test reporting (KAFKA-12216)

Hi folks, I have been playing with `reports.junitXml.mergeReruns` setting in gradle [1]. From the gradle doc: > When mergeReruns is enabled, if a test fails but is then retried and succeeds, its failures will be recorded as instead of , within one . This is effectively the reporting produced by