[PR] Send Poll event to the background thread [kafka]

2023-12-17 Thread via GitHub
philipnee opened a new pull request, #15035: URL: https://github.com/apache/kafka/pull/15035 *More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.* *Summary of testi

Re: [PR] MINOR: Fix typo [kafka]

2023-12-17 Thread via GitHub
JoeCqupt commented on PR #15031: URL: https://github.com/apache/kafka/pull/15031#issuecomment-1859590805 @ijuma @showuon PTAL -- 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 specific comment

Re: [PR] KAFKA-16012: Ensure new leader information merged correctly with the current metadata [kafka]

2023-12-17 Thread via GitHub
philipnee commented on PR #15023: URL: https://github.com/apache/kafka/pull/15023#issuecomment-1859575507 Here is the test results ``` SESSION REPORT (ALL TESTS) ducktape version: 0.8.14 session_i

[PR] RecordHeaders supports the addAll method [kafka]

2023-12-17 Thread via GitHub
funky-eyes opened a new pull request, #15034: URL: https://github.com/apache/kafka/pull/15034 *More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.* I think this cha

Re: [PR] KAFKA-15456: Commit/Fetch error handling improvements and V9 support [kafka]

2023-12-17 Thread via GitHub
lianetm commented on code in PR #14557: URL: https://github.com/apache/kafka/pull/14557#discussion_r1429362412 ## clients/src/main/java/org/apache/kafka/clients/consumer/internals/AsyncKafkaConsumer.java: ## @@ -1119,8 +1125,11 @@ public void commitSync(Map offsets, Duration

Re: [PR] KAFKA-15456: Commit/Fetch error handling improvements and V9 support [kafka]

2023-12-17 Thread via GitHub
lianetm commented on code in PR #14557: URL: https://github.com/apache/kafka/pull/14557#discussion_r1429362412 ## clients/src/main/java/org/apache/kafka/clients/consumer/internals/AsyncKafkaConsumer.java: ## @@ -1119,8 +1125,11 @@ public void commitSync(Map offsets, Duration

[jira] [Updated] (KAFKA-16025) Streams StateDirectory has orphaned locks after rebalancing, blocking future rebalancing

2023-12-17 Thread Sabit (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sabit updated KAFKA-16025: -- Description: Hello,   We are encountering an issue where during rebalancing, we see streams threads on one

[jira] [Updated] (KAFKA-16025) Streams StateDirectory has orphaned locks after rebalancing, blocking future rebalancing

2023-12-17 Thread Sabit (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sabit updated KAFKA-16025: -- Description: Hello,   We are encountering an issue where during rebalancing, we see streams threads on one

[jira] [Updated] (KAFKA-16025) Streams StateDirectory has orphaned locks after rebalancing, blocking future rebalancing

2023-12-17 Thread Sabit (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sabit updated KAFKA-16025: -- Description: Hello,   We are encountering an issue where during rebalancing, we see streams threads on one

[jira] [Created] (KAFKA-16025) Streams StateDirectory has orphaned locks after rebalancing, blocking future rebalancing

2023-12-17 Thread Sabit (Jira)
Sabit created KAFKA-16025: - Summary: Streams StateDirectory has orphaned locks after rebalancing, blocking future rebalancing Key: KAFKA-16025 URL: https://issues.apache.org/jira/browse/KAFKA-16025 Project: K

[jira] [Updated] (KAFKA-16025) Streams StateDirectory has orphaned locks after rebalancing, blocking future rebalancing

2023-12-17 Thread Sabit (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sabit updated KAFKA-16025: -- Description: Hello,   We are encountering an issue where during rebalancing, we see streams threads on one

Re: [PR] KAFKA-15270: Integration tests for new consumer [kafka]

2023-12-17 Thread via GitHub
lianetm closed pull request #14466: KAFKA-15270: Integration tests for new consumer URL: https://github.com/apache/kafka/pull/14466 -- 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 specific comme

Re: [PR] KAFKA-15270: Integration tests for new consumer [kafka]

2023-12-17 Thread via GitHub
lianetm commented on PR #14466: URL: https://github.com/apache/kafka/pull/14466#issuecomment-1859260551 Closed as existing PlainTextConsumerTests have been already parametrized to support the new protocol/consumer. -- This is an automated message from the Apache Git Service. To respond to

[PR] MINOR: Client state machine fix for transition to stable on initial empty assignment [kafka]

2023-12-17 Thread via GitHub
lianetm opened a new pull request, #15033: URL: https://github.com/apache/kafka/pull/15033 This includes a fix for ensuring that a member transitions to STABLE when joining a group, in the case where it receives an initial empty assignment. -- This is an automated message from the Ap

[jira] [Commented] (KAFKA-16003) The znode /config/topics is not updated during KRaft migration in "dual-write" mode

2023-12-17 Thread Mickael Maison (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797957#comment-17797957 ] Mickael Maison commented on KAFKA-16003: [~davidarthur] I think we should includ

[jira] [Updated] (KAFKA-16024) SaslPlaintextConsumerTest#testCoordinatorFailover is flaky

2023-12-17 Thread Philip Nee (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Nee updated KAFKA-16024: --- Parent: KAFKA-14246 Issue Type: Sub-task (was: Bug) > SaslPlaintextConsumerTest#testCoordin

[jira] [Created] (KAFKA-16024) SaslPlaintextConsumerTest#testCoordinatorFailover is flaky

2023-12-17 Thread Philip Nee (Jira)
Philip Nee created KAFKA-16024: -- Summary: SaslPlaintextConsumerTest#testCoordinatorFailover is flaky Key: KAFKA-16024 URL: https://issues.apache.org/jira/browse/KAFKA-16024 Project: Kafka Issue

[PR] KAFKA-15874: Add metric and request log attribute for deprecated request api versions (KIP-896) [kafka]

2023-12-17 Thread via GitHub
ijuma opened a new pull request, #15032: URL: https://github.com/apache/kafka/pull/15032 Breakdown of this PR: * Extend the generator to support deprecated api versions * Set deprecated api versions via the request json files * Expose the information via metrics and the request log

Re: [PR] KAFKA-15696: Refactor closing consumer [kafka]

2023-12-17 Thread via GitHub
philipnee commented on PR #14937: URL: https://github.com/apache/kafka/pull/14937#issuecomment-1859230526 Thanks @lucasbru -- 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 specific comment.

[PR] MINOR: Fix typo [kafka]

2023-12-17 Thread via GitHub
JoeCqupt opened a new pull request, #15031: URL: https://github.com/apache/kafka/pull/15031 *More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.* *Summary of testin

[jira] [Commented] (KAFKA-16015) kafka-leader-election timeout values always overwritten by default values

2023-12-17 Thread Sergio Troiano (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797933#comment-17797933 ] Sergio Troiano commented on KAFKA-16015: Pr open, [https://github.com/apache/ka

[PR] [KAFKA-16015] Fix custom timeouts overwritten by defaults [kafka]

2023-12-17 Thread via GitHub
sciclon2 opened a new pull request, #15030: URL: https://github.com/apache/kafka/pull/15030 ### Summary Basically when executing `kafka-leader-election.sh` the custom timeouts passed by the config file (--admin.config option) is not honoured. SO after [this investigation](https://issues.

Re: [PR] KAFKA-16023: Disable flaky tests [kafka]

2023-12-17 Thread via GitHub
lucasbru merged PR #15025: URL: https://github.com/apache/kafka/pull/15025 -- 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 specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache

Re: [PR] KAFKA-15696: Refactor closing consumer [kafka]

2023-12-17 Thread via GitHub
lucasbru commented on PR #14937: URL: https://github.com/apache/kafka/pull/14937#issuecomment-1859087131 @philipnee I think part of the reason why things are running particularly bad this weekend might be a change in transaction tests. I proposed a revert here. https://github.com/apache/kaf

Re: [PR] KAFKA-15764: Missing Tests for Transactions [kafka]

2023-12-17 Thread via GitHub
lucasbru commented on PR #14702: URL: https://github.com/apache/kafka/pull/14702#issuecomment-1859085537 @jolshan This PR might indeed be cursed. We have been seeing a lot of failures of `TransactionsWithTieredStoreTest.testTransactionsWithCompression` on trunk, and it seems to start with t

[PR] Revert "KAFKA-15764: Missing Tests for Transactions (#14702)" [kafka]

2023-12-17 Thread via GitHub
lucasbru opened a new pull request, #15029: URL: https://github.com/apache/kafka/pull/15029 This reverts commit ed7ad6d9d3d38940fbeb13324a186d3e5edd539e. We have been seeing a lot of failures of `TransactionsWithTieredStoreTest.testTransactionsWithCompression` on trunk, and it seems

Re: [PR] KAFKA-15696: Refactor closing consumer [kafka]

2023-12-17 Thread via GitHub
lucasbru commented on PR #14937: URL: https://github.com/apache/kafka/pull/14937#issuecomment-1859081002 @philipnee If tests are flaky in the PR that are also flaky on trunk, I don't think this is blocking the merge given the current state of the CI. The problem is that the builds fail comp