[jira] [Resolved] (KAFKA-15373) AdminClient#describeTopics should not throw InvalidTopicException if topic ID is not found

[ https://issues.apache.org/jira/browse/KAFKA-15373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Edgar resolved KAFKA-15373. --- Fix Version/s: 3.8.0 Resolution: Fixed > AdminClient#describeTopics should not throw

[jira] [Created] (KAFKA-17582) Unpredictable consumer position after transaction abort

Kyle Kingsbury created KAFKA-17582: -- Summary: Unpredictable consumer position after transaction abort Key: KAFKA-17582 URL: https://issues.apache.org/jira/browse/KAFKA-17582 Project: Kafka I

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

Hi David, Thanks for your helpful suggestions, which make this KIP clearer. I have revised the content according to your feedback. Regarding the fourth point, I agree that the original description was imprecise and could lead to misunderstandings. Since this is not new behavior, I have removed it

Re: [DISCUSS] - Kafka topic deletion improvement

Hey Murali, Thanks for raising this. I think it would make sense to take another look at the dependencies between the different CRUD objects that Kafka exposes, and add some sanity checks where they make sense and can be implemented safely. I was just speaking to a user that had some confusion f

Re: [DISCUSS] - Kafka topic deletion improvement

Thank you Greg for your inputs. In addition to my previous proposal, below we can add if they make sense. 1. Acl clean up cli: For all the non existent topics, find all the acls, show a preview in dry run mode and execute ./acl-cleanup.sh --mode dryrun/execute Need to be careful of the wildcar

[jira] [Created] (KAFKA-17580) Java 21 spurious compilation failure

David Arthur created KAFKA-17580: Summary: Java 21 spurious compilation failure Key: KAFKA-17580 URL: https://issues.apache.org/jira/browse/KAFKA-17580 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-1089: Allow disabling heartbeats replication in MirrorSourceConnector

Bump - I know this is not a complicated proposal, but if you have any inputs, please share. TIA, Daniel Dániel Urbán ezt írta (időpont: 2024. szept. 13., P, 16:54): > Hi Viktor, > Thanks for your comments. Technically, yes, a policy subclass can be used > to intentionally misconfigure the heartb

[jira] [Resolved] (KAFKA-17515) Fix flaky RestoreIntegrationTest.shouldInvokeUserDefinedGlobalStateRestoreListener

[ https://issues.apache.org/jira/browse/KAFKA-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17515. Fix Version/s: 4.0.0 Resolution: Fixed > Fix flaky > RestoreIntegrationTest.should

[jira] [Resolved] (KAFKA-17553) DefaultTaskManager.shutdown stalling on Github CI

[ https://issues.apache.org/jira/browse/KAFKA-17553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17553. Fix Version/s: 4.0.0 Assignee: David Arthur Resolution: Fixed > DefaultTas

[jira] [Created] (KAFKA-17579) Dynamic LogCleaner configurations are not picked up upon restart

Christo Lolov created KAFKA-17579: - Summary: Dynamic LogCleaner configurations are not picked up upon restart Key: KAFKA-17579 URL: https://issues.apache.org/jira/browse/KAFKA-17579 Project: Kafka

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

See

Re: New release branch 3.9

Hi Colin, I have a minor improvement to the rendering of our documentation that we should include in 3.9: https://github.com/apache/kafka/pull/17235 Thanks -Jose

[jira] [Created] (KAFKA-17581) AsyncKafkaConsumer can't unsubscribe invalid topics

PoAn Yang created KAFKA-17581: - Summary: AsyncKafkaConsumer can't unsubscribe invalid topics Key: KAFKA-17581 URL: https://issues.apache.org/jira/browse/KAFKA-17581 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

Hi David, Thanks for the explanation. I like this two-tiered approach, which gives us more flexibility to handle flaky tests. The following is my understanding of how it works; please correct me if I'm wrong: If we adopt the two-tiered approach, the test might have two states.(Isolated by develo

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

> However, this doesn't help with the newly added tests that introduce flakiness. For this, we need some way to detect when a new test has been added. Still thinking through this... Maybe we can use git + gradle develocity to address it. 1) list the files changed recently (for example: git diff -

[jira] [Resolved] (KAFKA-17356) add integration test for KAFKA-17310

[ https://issues.apache.org/jira/browse/KAFKA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17356. Fix Version/s: 4.0.0 Resolution: Fixed > add integration test for KAFKA-17310 > ---

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

TengYao, > These two mechanisms are independent. We could manually remove a tag from a test, but at the same time, it might still be quarantined. I know the above situation might sound weird, but I just want to understand how it would work. If we remove a tag from a test, we are signaling that we

[jira] [Resolved] (KAFKA-17557) Test123

[ https://issues.apache.org/jira/browse/KAFKA-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-17557. --- Resolution: Invalid > Test123 > --- > > Key: KAFKA-17557 >

[jira] [Resolved] (KAFKA-17555) uncomment all checks of testCommonNameLoggingTrustManagerMixValidAndInvalidCertificates

[ https://issues.apache.org/jira/browse/KAFKA-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17555. Fix Version/s: 4.0.0 Resolution: Fixed > uncomment all checks of > testCommonNameL

[DISCUSS] - Kafka topic deletion improvement

Hello everyone, I’d like to propose an improvement to the Kafka topic deletion process, specifically regarding ACLs. Currently, when we delete a topic using the kafka-topics.sh cli, the topic is removed without any consideration for the ACLs that were applied to it. This could lead to stale ACLs

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

hi David The two-tiered approach is interesting and I have questions similar to TengYao. BUT, go back to the usage of quarantine and isolation. It seems to me they are used to make our CI not be noised by the flaky, right? If so, could we query the Gradle develocity to get flaky and then make onl

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

Chia/TengYao/TaiJuWu, I agree that tags are a straightforward approach. In fact, my initial idea was to use tags as the isolation mechanism. Let me try to motivate the use of a text file a bit more. Consider the "new tests" scenario where a developer has added a new integration test. If we use an

Re: [DISCUSS] KIP-1021: Allow to get last stable offset (LSO) in kafka-get-offsets.sh

Hi Ahmed, Are you still interested in this KIP? Should we take it over if you're busy on other things? Thanks. Luke On Wed, Mar 27, 2024 at 12:26 PM Kamal Chandraprakash < kamal.chandraprak...@gmail.com> wrote: > Hi Ahmed, > > Thanks for the KIP! It will be a useful addition to know the > last

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

Hi, Thanks for the update. I have a few nits: > If the member ID is null or empty, the server will reject the request with an InvalidRequestException. We should clarify that this should only apply to version >= 1. > The consumer instance must generate a member ID, and this ID should remain consi