[jira] [Created] (KAFKA-13981) metadata shell doesn't recognize some new record types

Luke Chen created KAFKA-13981: - Summary: metadata shell doesn't recognize some new record types Key: KAFKA-13981 URL: https://issues.apache.org/jira/browse/KAFKA-13981 Project: Kafka Issue Type:

[GitHub] [kafka] showuon commented on a diff in pull request #12179: [KAFKA-13848] Clients remain connected after SASL re-authentication f…

showuon commented on code in PR #12179: URL: https://github.com/apache/kafka/pull/12179#discussion_r895290288 ## build.gradle: ## @@ -1243,7 +1243,7 @@ project(':clients') { testImplementation libs.bcpkix testImplementation libs.junitJupiter -testImplementation

[jira] [Resolved] (KAFKA-13891) sync group failed with rebalanceInProgress error cause rebalance many rounds in coopeartive

[ https://issues.apache.org/jira/browse/KAFKA-13891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13891. --- Fix Version/s: 3.3.0 Resolution: Fixed > sync group failed with rebalanceInProgress error

[GitHub] [kafka] showuon merged pull request #12140: KAFKA-13891: reset generation when syncgroup failed with REBALANCE_IN_PROGRESS

showuon merged PR #12140: URL: https://github.com/apache/kafka/pull/12140 -- 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:

[GitHub] [kafka] showuon commented on pull request #12140: KAFKA-13891: reset generation when syncgroup failed with REBALANCE_IN_PROGRESS

showuon commented on PR #12140: URL: https://github.com/apache/kafka/pull/12140#issuecomment-1153399981 Failed tests are unrelated ``` Build / JDK 11 and Scala 2.13 / kafka.server.MultipleListenersWithDefaultJaasContextTest.testProduceConsume() Build / JDK 11 and Scala 2.13

[jira] [Resolved] (KAFKA-13977) internal topic deserialize failed

[ https://issues.apache.org/jira/browse/KAFKA-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jeff-qiu resolved KAFKA-13977. -- Resolution: Not A Problem sorry about it,this is not a kafka problem. > internal topic deserialize

[jira] [Closed] (KAFKA-13977) internal topic deserialize failed

[ https://issues.apache.org/jira/browse/KAFKA-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jeff-qiu closed KAFKA-13977. > internal topic deserialize failed > - > > Key: KAFKA-13977

[GitHub] [kafka] C0urante commented on a diff in pull request #11782: KAFKA-10000: Integration tests (KIP-618)

C0urante commented on code in PR #11782: URL: https://github.com/apache/kafka/pull/11782#discussion_r895251747 ## connect/runtime/src/main/java/org/apache/kafka/connect/runtime/rest/resources/ConnectorsResource.java: ## @@ -340,6 +340,7 @@ public void putTaskConfigs(final

[GitHub] [kafka] C0urante commented on pull request #11782: KAFKA-10000: Integration tests (KIP-618)

C0urante commented on PR #11782: URL: https://github.com/apache/kafka/pull/11782#issuecomment-1153328287 Added a line to `ConnectorsResource` to hide the newly-introduced zombie fencing API from the OpenAPI spec that we started generating with https://github.com/apache/kafka/pull/12067.

[GitHub] [kafka] splett2 commented on a diff in pull request #12194: MINOR: Include listener name in SocketServer acceptor and processor log context

splett2 commented on code in PR #12194: URL: https://github.com/apache/kafka/pull/12194#discussion_r895227215 ## core/src/main/scala/kafka/network/SocketServer.scala: ## @@ -242,13 +241,14 @@ class SocketServer(val config: KafkaConfig, } private def endpoints =

[GitHub] [kafka] splett2 commented on pull request #12194: MINOR: Include listener name in SocketServer acceptor and processor log context

splett2 commented on PR #12194: URL: https://github.com/apache/kafka/pull/12194#issuecomment-1153279565 Thank you for the reviews. @mimaison technically we don't, but the reason I chose to preserve that part of the log context is because it is inherited by `NioSelector` created

[GitHub] [kafka] ijuma commented on pull request #11261: KAFKA-13228: ApiVersionRequest is not properly handled in KRaft co-resident mode

ijuma commented on PR #11261: URL: https://github.com/apache/kafka/pull/11261#issuecomment-1153261781 Was this fixed some other way? -- 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

[jira] [Commented] (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:comment-tabpanel=17553315#comment-17553315 ] Ismael Juma commented on KAFKA-12639: - Is this related to

[GitHub] [kafka] aiquestion commented on a diff in pull request #12140: KAFKA-13891: reset generation when syncgroup failed with REBALANCE_IN_PROGRESS

aiquestion commented on code in PR #12140: URL: https://github.com/apache/kafka/pull/12140#discussion_r895151185 ## clients/src/test/java/org/apache/kafka/clients/consumer/internals/AbstractCoordinatorTest.java: ## @@ -488,6 +489,54 @@ public void

[GitHub] [kafka] showuon commented on a diff in pull request #12140: KAFKA-13891: reset generation when syncgroup failed with REBALANCE_IN_PROGRESS

showuon commented on code in PR #12140: URL: https://github.com/apache/kafka/pull/12140#discussion_r895147723 ## clients/src/test/java/org/apache/kafka/clients/consumer/internals/AbstractCoordinatorTest.java: ## @@ -488,6 +489,54 @@ public void

[GitHub] [kafka] divijvaidya commented on pull request #12285: KAFKA-7342 Part 1: Straightforward JUnit4 to JUnit5 migrations

divijvaidya commented on PR #12285: URL: https://github.com/apache/kafka/pull/12285#issuecomment-1153118745 Thanks you submitting this change @clolov. This would greatly help us in moving towards getting rid of JUnit4 completely. 1\ To make the code review easier, could we please

[GitHub] [kafka] aiquestion commented on pull request #12140: KAFKA-13891: reset generation when syncgroup failed with REBALANCE_IN_PROGRESS

aiquestion commented on PR #12140: URL: https://github.com/apache/kafka/pull/12140#issuecomment-1153106554 > @aiquestion , thanks for the PR. Could we add a test for it? @showuon sorry for the delay. What should i do to get this PR merged? ( it's my first time submit a PR ) --

[GitHub] [kafka] aiquestion commented on a diff in pull request #12140: KAFKA-13891: reset generation when syncgroup failed with REBALANCE_IN_PROGRESS

aiquestion commented on code in PR #12140: URL: https://github.com/apache/kafka/pull/12140#discussion_r895136385 ## clients/src/test/java/org/apache/kafka/clients/consumer/internals/AbstractCoordinatorTest.java: ## @@ -488,6 +489,54 @@ public void

[GitHub] [kafka] Kvicii commented on pull request #12285: KAFKA-7342 Part 1: Straightforward JUnit4 to JUnit5 migrations

Kvicii commented on PR #12285: URL: https://github.com/apache/kafka/pull/12285#issuecomment-1153094346 @clolov thanks your PR, I think we should multiple modify. @divijvaidya @dengziming @mimaison Do you have any better suggestion? -- This is an automated message from the Apache Git

[GitHub] [kafka] clolov commented on pull request #12285: KAFKA-7342 Part 1: Straightforward JUnit4 to JUnit5 migrations

clolov commented on PR #12285: URL: https://github.com/apache/kafka/pull/12285#issuecomment-1153084216 Polite ask for a review from @divijvaidya @dengziming @Kvicii @mimaison. The decisions I have outlined in the description are reversible should there be objections to them :) -- This

[GitHub] [kafka] clolov opened a new pull request, #12285: KAFKA-7342 Part 1: Straightforward JUnit4 to JUnit5 migrations

clolov opened a new pull request, #12285: URL: https://github.com/apache/kafka/pull/12285 This is the first part of KAFKA-7342 (https://issues.apache.org/jira/browse/KAFKA-7342). Here are the decisions I made in this change: * Do not (yet) migrate files using Parameterized because they