[jira] [Resolved] (KAFKA-13767) Fetch from consumers should return immediately when preferred read replica is defined by the leader

[ https://issues.apache.org/jira/browse/KAFKA-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13767. - Reviewer: David Jacot Resolution: Fixed > Fetch from consumers should return immediately

[jira] [Assigned] (KAFKA-13767) Fetch from consumers should return immediately when preferred read replica is defined by the leader

[ https://issues.apache.org/jira/browse/KAFKA-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13767: --- Assignee: zhaobo > Fetch from consumers should return immediately when preferred read

[jira] [Updated] (KAFKA-13767) Fetch from consumers should return immediately when preferred read replica is defined by the leader

[ https://issues.apache.org/jira/browse/KAFKA-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13767: Affects Version/s: 2.4.0 (was: 3.2.0) > Fetch from consumers should

[jira] [Assigned] (KAFKA-13766) Use `max.poll.interval.ms` as the timeout during complete-rebalance phase

[ https://issues.apache.org/jira/browse/KAFKA-13766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13766: --- Assignee: David Jacot > Use `max.poll.interval.ms` as the timeout during

[jira] [Commented] (KAFKA-13457) SocketChannel in Acceptor#accept is not closed upon IOException

[ https://issues.apache.org/jira/browse/KAFKA-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510466#comment-17510466 ] David Jacot commented on KAFKA-13457: - [~mimaison] Done. > SocketChannel in Acceptor#accept is not

[jira] [Closed] (KAFKA-13457) SocketChannel in Acceptor#accept is not closed upon IOException

[ https://issues.apache.org/jira/browse/KAFKA-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot closed KAFKA-13457. --- > SocketChannel in Acceptor#accept is not closed upon IOException >

[jira] [Closed] (KAFKA-13457) SocketChannel in Acceptor#accept is not closed upon IOException

[ https://issues.apache.org/jira/browse/KAFKA-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot closed KAFKA-13457. --- > SocketChannel in Acceptor#accept is not closed upon IOException >

[jira] [Resolved] (KAFKA-13752) Using `equals` instead of `==` when Uuid compare in Java

[ https://issues.apache.org/jira/browse/KAFKA-13752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13752. - Fix Version/s: 3.2.0 3.1.1 3.3.0 Resolution: Fixed

[jira] [Commented] (KAFKA-13752) Using `equals` instead of `==` when Uuid compare in Java

[ https://issues.apache.org/jira/browse/KAFKA-13752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17510330#comment-17510330 ] David Jacot commented on KAFKA-13752: - There is no real impact because we always use UUID.ZERO_UUID

[jira] [Commented] (KAFKA-13422) Even if the correct username and password are configured, when ClientBroker or KafkaClient tries to establish a SASL connection to ServerBroker, an exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508813#comment-17508813 ] David Jacot commented on KAFKA-13422: - > But for ClientBroker, it also needs to play the role of

[jira] [Commented] (KAFKA-13751) On the broker side, OAUTHBEARER is not compatible with other SASL mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508806#comment-17508806 ] David Jacot commented on KAFKA-13751: - [~RivenSun] I am not sure to fully understand your point

[jira] [Commented] (KAFKA-13422) Even if the correct username and password are configured, when ClientBroker or KafkaClient tries to establish a SASL connection to ServerBroker, an exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508755#comment-17508755 ] David Jacot commented on KAFKA-13422: - > But it makes sense to configure multiple loginModule in

[jira] [Commented] (KAFKA-13422) Even if the correct username and password are configured, when ClientBroker or KafkaClient tries to establish a SASL connection to ServerBroker, an exception is thrown

[ https://issues.apache.org/jira/browse/KAFKA-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508722#comment-17508722 ] David Jacot commented on KAFKA-13422: - [~RivenSun] Thanks for reporting this and for the analysis.

[jira] [Resolved] (KAFKA-13497) Debug Log RegexRouter transform

[ https://issues.apache.org/jira/browse/KAFKA-13497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13497. - Fix Version/s: 3.2.0 Reviewer: David Jacot Resolution: Fixed > Debug Log

[jira] [Commented] (KAFKA-13584) Fix `kafka.network.SocketServerTest.testUnmuteChannelWithBufferedReceives` flaky test

[ https://issues.apache.org/jira/browse/KAFKA-13584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508636#comment-17508636 ] David Jacot commented on KAFKA-13584: - This commit

[jira] [Resolved] (KAFKA-13584) Fix `kafka.network.SocketServerTest.testUnmuteChannelWithBufferedReceives` flaky test

[ https://issues.apache.org/jira/browse/KAFKA-13584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13584. - Resolution: Fixed Fixed by

[jira] [Resolved] (KAFKA-13750) Client Compatability KafkaTest uses invalid idempotency configs

[ https://issues.apache.org/jira/browse/KAFKA-13750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13750. - Fix Version/s: 3.2.0 3.1.1 3.0.2 Resolution: Fixed

[jira] [Resolved] (KAFKA-13509) Support max timestamp in GetOffsetShell

[ https://issues.apache.org/jira/browse/KAFKA-13509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13509. - Reviewer: David Jacot Resolution: Fixed > Support max timestamp in GetOffsetShell >

[jira] [Resolved] (KAFKA-13706) org.apache.kafka.test.MockSelector doesn't remove closed connections from its 'ready' field

[ https://issues.apache.org/jira/browse/KAFKA-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13706. - Fix Version/s: 3.2.0 Reviewer: David Jacot Assignee: Vincent Jiang

[jira] [Resolved] (KAFKA-13435) Static membership protocol should let the leader skip assignment (KIP-814)

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13435. - Reviewer: Jason Gustafson Resolution: Fixed > Static membership protocol should let the

[jira] [Updated] (KAFKA-13435) Static membership protocol should let the leader skip assignment (KIP-814)

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13435: Summary: Static membership protocol should let the leader skip assignment (KIP-814) (was: Group

[jira] [Resolved] (KAFKA-13636) Committed offsets could be deleted during a rebalance if a group did not commit for a while

[ https://issues.apache.org/jira/browse/KAFKA-13636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13636. - Fix Version/s: 3.0.1 2.8.2 3.2.0 3.1.1

[jira] [Resolved] (KAFKA-13583) Fix FetchRequestBetweenDifferentIbpTest flaky tests

[ https://issues.apache.org/jira/browse/KAFKA-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13583. - Fix Version/s: 3.2.0 3.1.1 Reviewer: David Jacot Resolution:

[jira] [Resolved] (KAFKA-13637) User default.api.timeout.ms config as default timeout for KafkaConsumer.endOffsets

[ https://issues.apache.org/jira/browse/KAFKA-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13637. - Fix Version/s: 3.0.1 3.2.0 3.1.1 Reviewer: David

[jira] [Assigned] (KAFKA-13636) Committed offsets could be deleted during a rebalance if a group did not commit for a while

[ https://issues.apache.org/jira/browse/KAFKA-13636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13636: --- Assignee: David Jacot > Committed offsets could be deleted during a rebalance if a group

[jira] [Resolved] (KAFKA-13614) Leader replication quota is applied to consumer fetches

[ https://issues.apache.org/jira/browse/KAFKA-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13614. - Fix Version/s: 3.2.0 Reviewer: David Jacot Resolution: Fixed > Leader

[jira] [Resolved] (KAFKA-13585) Fix `kafka.server.ReplicaManagerTest.testReplicaAlterLogDirsWithAndWithoutIds` flaky test

[ https://issues.apache.org/jira/browse/KAFKA-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13585. - Fix Version/s: 3.2.0 3.1.1 Reviewer: Jason Gustafson

[jira] [Resolved] (KAFKA-13388) Kafka Producer nodes stuck in CHECKING_API_VERSIONS

[ https://issues.apache.org/jira/browse/KAFKA-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13388. - Fix Version/s: 3.0.1 3.2.0 3.1.1 Reviewer: Rajini

[jira] [Resolved] (KAFKA-13591) Fix flaky test ControllerIntegrationTest.testTopicIdCreatedOnUpgrade

[ https://issues.apache.org/jira/browse/KAFKA-13591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13591. - Fix Version/s: 3.2.0 3.1.1 Reviewer: Jason Gustafson

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478765#comment-17478765 ] David Jacot commented on KAFKA-13435: - [~rleslie] I have published a small KIP to address this

[jira] [Commented] (KAFKA-13598) producer config didn't throw exception when retries and acks config changed

[ https://issues.apache.org/jira/browse/KAFKA-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478455#comment-17478455 ] David Jacot commented on KAFKA-13598: - Sounds good. Thanks [~showuon]. > producer config didn't

[jira] [Updated] (KAFKA-13598) producer config didn't throw exception when retries and acks config changed

[ https://issues.apache.org/jira/browse/KAFKA-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13598: Fix Version/s: 3.1.1 3.2.0 > producer config didn't throw exception when

[jira] [Comment Edited] (KAFKA-13598) producer config didn't throw exception when retries and acks config changed

[ https://issues.apache.org/jira/browse/KAFKA-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478086#comment-17478086 ] David Jacot edited comment on KAFKA-13598 at 1/18/22, 5:55 PM: --- That seems

[jira] [Commented] (KAFKA-13598) producer config didn't throw exception when retries and acks config changed

[ https://issues.apache.org/jira/browse/KAFKA-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478086#comment-17478086 ] David Jacot commented on KAFKA-13598: - That seems to be a bug and not a regression introduced in 3.1

[jira] [Commented] (KAFKA-13592) Fix flaky test ControllerIntegrationTest.testTopicIdUpgradeAfterReassigningPartitions

[ https://issues.apache.org/jira/browse/KAFKA-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477657#comment-17477657 ] David Jacot commented on KAFKA-13592: - [~Kvicii] I don't know the reason of this issue... However, I

[jira] [Commented] (KAFKA-13592) Fix flaky test ControllerIntegrationTest.testTopicIdUpgradeAfterReassigningPartitions

[ https://issues.apache.org/jira/browse/KAFKA-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17477048#comment-17477048 ] David Jacot commented on KAFKA-13592: - [~Kvicii] Of course! Go for it. I think that the issue might

[jira] [Resolved] (KAFKA-13451) Add reason to JoinGroupRequest and LeaveGroupRequest

[ https://issues.apache.org/jira/browse/KAFKA-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13451. - Fix Version/s: 3.2.0 Reviewer: David Jacot Resolution: Fixed > Add reason to

[jira] [Resolved] (KAFKA-13496) Add reason to LeaveGroupRequest

[ https://issues.apache.org/jira/browse/KAFKA-13496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13496. - Fix Version/s: 3.2.0 Reviewer: David Jacot Resolution: Fixed > Add reason to

[jira] [Resolved] (KAFKA-13495) Add reason to JoinGroupRequest

[ https://issues.apache.org/jira/browse/KAFKA-13495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13495. - Fix Version/s: 3.2.0 Reviewer: David Jacot Resolution: Fixed > Add reason to

[jira] [Created] (KAFKA-13592) Fix flaky test ControllerIntegrationTest.testTopicIdUpgradeAfterReassigningPartitions

David Jacot created KAFKA-13592: --- Summary: Fix flaky test ControllerIntegrationTest.testTopicIdUpgradeAfterReassigningPartitions Key: KAFKA-13592 URL: https://issues.apache.org/jira/browse/KAFKA-13592

[jira] [Assigned] (KAFKA-13591) Fix flaky test ControllerIntegrationTest.testTopicIdCreatedOnUpgrade

[ https://issues.apache.org/jira/browse/KAFKA-13591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13591: --- Assignee: David Jacot > Fix flaky test

[jira] [Created] (KAFKA-13591) Fix flaky test ControllerIntegrationTest.testTopicIdCreatedOnUpgrade

David Jacot created KAFKA-13591: --- Summary: Fix flaky test ControllerIntegrationTest.testTopicIdCreatedOnUpgrade Key: KAFKA-13591 URL: https://issues.apache.org/jira/browse/KAFKA-13591 Project: Kafka

[jira] [Updated] (KAFKA-13585) Fix `kafka.server.ReplicaManagerTest.testReplicaAlterLogDirsWithAndWithoutIds` flaky test

[ https://issues.apache.org/jira/browse/KAFKA-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13585: Priority: Minor (was: Major) > Fix >

[jira] [Assigned] (KAFKA-13585) Fix `kafka.server.ReplicaManagerTest.testReplicaAlterLogDirsWithAndWithoutIds` flaky test

[ https://issues.apache.org/jira/browse/KAFKA-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13585: --- Assignee: David Jacot > Fix >

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472085#comment-17472085 ] David Jacot commented on KAFKA-13435: - Thanks, [~hachikuji]. I think that AK assignors are usually

[jira] [Commented] (KAFKA-13582) `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails

[ https://issues.apache.org/jira/browse/KAFKA-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472026#comment-17472026 ] David Jacot commented on KAFKA-13582: - I have reduced the priority to Major as it is purely a

[jira] [Updated] (KAFKA-13582) `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails

[ https://issues.apache.org/jira/browse/KAFKA-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13582: Priority: Major (was: Blocker) > `TestVerifiableProducer.

[jira] [Assigned] (KAFKA-13582) `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails

[ https://issues.apache.org/jira/browse/KAFKA-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13582: --- Assignee: Ron Dagostino > `TestVerifiableProducer. test_multiple_kraft_security_protocols`

[jira] [Created] (KAFKA-13585) Fix `kafka.server.ReplicaManagerTest.testReplicaAlterLogDirsWithAndWithoutIds` flaky test

David Jacot created KAFKA-13585: --- Summary: Fix `kafka.server.ReplicaManagerTest.testReplicaAlterLogDirsWithAndWithoutIds` flaky test Key: KAFKA-13585 URL: https://issues.apache.org/jira/browse/KAFKA-13585

[jira] [Created] (KAFKA-13584) Fix `kafka.network.SocketServerTest.testUnmuteChannelWithBufferedReceives` flaky test

David Jacot created KAFKA-13584: --- Summary: Fix `kafka.network.SocketServerTest.testUnmuteChannelWithBufferedReceives` flaky test Key: KAFKA-13584 URL: https://issues.apache.org/jira/browse/KAFKA-13584

[jira] [Updated] (KAFKA-13583) Fix FetchRequestBetweenDifferentIbpTest flaky tests

[ https://issues.apache.org/jira/browse/KAFKA-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13583: Description: FetchRequestBetweenDifferentIbpTest's tests often fails with: {noformat}

[jira] [Created] (KAFKA-13583) Fix FetchRequestBetweenDifferentIbpTest flaky tests

David Jacot created KAFKA-13583: --- Summary: Fix FetchRequestBetweenDifferentIbpTest flaky tests Key: KAFKA-13583 URL: https://issues.apache.org/jira/browse/KAFKA-13583 Project: Kafka Issue

[jira] [Updated] (KAFKA-13582) `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails

[ https://issues.apache.org/jira/browse/KAFKA-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13582: Description: `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails

[jira] [Created] (KAFKA-13582) `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails

David Jacot created KAFKA-13582: --- Summary: `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails Key: KAFKA-13582 URL: https://issues.apache.org/jira/browse/KAFKA-13582

[jira] [Resolved] (KAFKA-13312) 'NetworkDegradeTest#test_rate' should wait until iperf server is listening

[ https://issues.apache.org/jira/browse/KAFKA-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13312. - Resolution: Fixed > 'NetworkDegradeTest#test_rate' should wait until iperf server is listening

[jira] [Resolved] (KAFKA-10712) Update release scripts to Python3

[ https://issues.apache.org/jira/browse/KAFKA-10712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10712. - Fix Version/s: 3.1.0 Resolution: Fixed > Update release scripts to Python3 >

[jira] [Updated] (KAFKA-13488) Producer fails to recover if topic gets deleted (and gets auto-created)

[ https://issues.apache.org/jira/browse/KAFKA-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13488: Fix Version/s: (was: 3.2.0) > Producer fails to recover if topic gets deleted (and gets

[jira] [Updated] (KAFKA-13488) Producer fails to recover if topic gets deleted (and gets auto-created)

[ https://issues.apache.org/jira/browse/KAFKA-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13488: Fix Version/s: 3.0.1 2.8.2 3.2.0 > Producer fails to

[jira] [Updated] (KAFKA-13488) Producer fails to recover if topic gets deleted (and gets auto-created)

[ https://issues.apache.org/jira/browse/KAFKA-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13488: Priority: Blocker (was: Major) > Producer fails to recover if topic gets deleted (and gets

[jira] [Updated] (KAFKA-13488) Producer fails to recover if topic gets deleted (and gets auto-created)

[ https://issues.apache.org/jira/browse/KAFKA-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13488: Fix Version/s: 3.1.0 > Producer fails to recover if topic gets deleted (and gets auto-created) >

[jira] [Assigned] (KAFKA-13388) Kafka Producer nodes stuck in CHECKING_API_VERSIONS

[ https://issues.apache.org/jira/browse/KAFKA-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13388: --- Assignee: David Jacot > Kafka Producer nodes stuck in CHECKING_API_VERSIONS >

[jira] [Commented] (KAFKA-13388) Kafka Producer nodes stuck in CHECKING_API_VERSIONS

[ https://issues.apache.org/jira/browse/KAFKA-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17457274#comment-17457274 ] David Jacot commented on KAFKA-13388: - I can think of a few ways to fix this: 1) We could decide to

[jira] [Commented] (KAFKA-13388) Kafka Producer nodes stuck in CHECKING_API_VERSIONS

[ https://issues.apache.org/jira/browse/KAFKA-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17457016#comment-17457016 ] David Jacot commented on KAFKA-13388: - I had a look at the code as well. [~david.mao] is right. My

[jira] [Updated] (KAFKA-13512) topicIdsToNames and topicNamesToIds allocate unnecessary maps

[ https://issues.apache.org/jira/browse/KAFKA-13512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13512: Fix Version/s: 3.1.0 > topicIdsToNames and topicNamesToIds allocate unnecessary maps >

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454118#comment-17454118 ] David Jacot commented on KAFKA-13435: - Let me summarise the options that we have discussed so far:

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452990#comment-17452990 ] David Jacot commented on KAFKA-13435: - I don't have the implementation details yet but the idea

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452494#comment-17452494 ] David Jacot commented on KAFKA-13435: - Yeah, I do agree that this solution does not fly if we can't

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17451896#comment-17451896 ] David Jacot commented on KAFKA-13435: - I have put a bit more thoughts into this and it seems that we

[jira] [Created] (KAFKA-13496) Add reason to LeaveGroupRequest

David Jacot created KAFKA-13496: --- Summary: Add reason to LeaveGroupRequest Key: KAFKA-13496 URL: https://issues.apache.org/jira/browse/KAFKA-13496 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-13495) Add reason to JoinGroupRequest

David Jacot created KAFKA-13495: --- Summary: Add reason to JoinGroupRequest Key: KAFKA-13495 URL: https://issues.apache.org/jira/browse/KAFKA-13495 Project: Kafka Issue Type: Sub-task

[jira] [Updated] (KAFKA-13451) Add reason to JoinGroupRequest and LeaveGroupRequest

[ https://issues.apache.org/jira/browse/KAFKA-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13451: Summary: Add reason to JoinGroupRequest and LeaveGroupRequest (was: Add reason to

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17451661#comment-17451661 ] David Jacot commented on KAFKA-13435: - [~rleslie] I understand your point. Manually restarting

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17451144#comment-17451144 ] David Jacot commented on KAFKA-13435: - I have looked into this issue and I do agree with

[jira] [Updated] (KAFKA-13069) Add magic number to DefaultKafkaPrincipalBuilder.KafkaPrincipalSerde

[ https://issues.apache.org/jira/browse/KAFKA-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13069: Fix Version/s: (was: 3.1.0) > Add magic number to

[jira] [Resolved] (KAFKA-13457) SocketChannel in Acceptor#accept is not closed upon IOException

[ https://issues.apache.org/jira/browse/KAFKA-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13457. - Fix Version/s: 3.2.0 Reviewer: David Jacot Resolution: Fixed > SocketChannel in

[jira] [Updated] (KAFKA-13457) SocketChannel in Acceptor#accept is not closed upon IOException

[ https://issues.apache.org/jira/browse/KAFKA-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13457: Summary: SocketChannel in Acceptor#accept is not closed upon IOException (was: socketChannel in

[jira] [Assigned] (KAFKA-9648) Add configuration to adjust listen backlog size for Acceptor

[ https://issues.apache.org/jira/browse/KAFKA-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-9648: -- Assignee: Haruki Okada > Add configuration to adjust listen backlog size for Acceptor >

[jira] [Updated] (KAFKA-9648) Add configuration to adjust listen backlog size for Acceptor

[ https://issues.apache.org/jira/browse/KAFKA-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-9648: --- Summary: Add configuration to adjust listen backlog size for Acceptor (was: kafka server should

[jira] [Resolved] (KAFKA-9648) Add configuration to adjust listen backlog size for Acceptor

[ https://issues.apache.org/jira/browse/KAFKA-9648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-9648. Fix Version/s: 3.2.0 Reviewer: David Jacot Resolution: Fixed > Add configuration

[jira] [Updated] (KAFKA-13451) Add reason to LeaveGroupRequest

[ https://issues.apache.org/jira/browse/KAFKA-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13451: Description: At the moment, when a member leaves a group, the java clients logs the reason.

[jira] [Commented] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444998#comment-17444998 ] David Jacot commented on KAFKA-13435: - [~rleslie] Thanks for reporting this bug. I have assigned the

[jira] [Assigned] (KAFKA-13435) Group won't consume partitions added after static member restart

[ https://issues.apache.org/jira/browse/KAFKA-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13435: --- Assignee: David Jacot > Group won't consume partitions added after static member restart >

[jira] [Resolved] (KAFKA-13449) Comment optimization for parameter log.cleaner.delete.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13449. - Fix Version/s: 3.2.0 Resolution: Fixed > Comment optimization for parameter

[jira] [Commented] (KAFKA-13444) Fix OAuthCompatibilityTool help and add SSL options

[ https://issues.apache.org/jira/browse/KAFKA-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444360#comment-17444360 ] David Jacot commented on KAFKA-13444: - [~kirktrue] Yes. It makes sense to include it in order to not

[jira] [Commented] (KAFKA-13411) Exception while connecting from kafka client consumer producers deployed in a wildfly context to a kafka broker implementing OAUTHBEARER sasl mechanism

[ https://issues.apache.org/jira/browse/KAFKA-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443714#comment-17443714 ] David Jacot commented on KAFKA-13411: - Moving this issue to the next release as we are past to code

[jira] [Updated] (KAFKA-13411) Exception while connecting from kafka client consumer producers deployed in a wildfly context to a kafka broker implementing OAUTHBEARER sasl mechanism

[ https://issues.apache.org/jira/browse/KAFKA-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13411: Fix Version/s: 3.2.0 (was: 3.1.0) > Exception while connecting from kafka

[jira] [Updated] (KAFKA-12283) Flaky Test RebalanceSourceConnectorsIntegrationTest#testMultipleWorkersRejoining

[ https://issues.apache.org/jira/browse/KAFKA-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12283: Fix Version/s: 3.2.0 (was: 3.1.0) > Flaky Test >

[jira] [Updated] (KAFKA-10642) Expose the real stack trace if any exception occurred during SSL Client Trust Verification in extension

[ https://issues.apache.org/jira/browse/KAFKA-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-10642: Fix Version/s: 3.2.0 (was: 3.1.0) > Expose the real stack trace if any

[jira] [Commented] (KAFKA-10642) Expose the real stack trace if any exception occurred during SSL Client Trust Verification in extension

[ https://issues.apache.org/jira/browse/KAFKA-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443710#comment-17443710 ] David Jacot commented on KAFKA-10642: - Moving to the next release as we are past the 3.1 release

[jira] [Commented] (KAFKA-12774) kafka-streams 2.8: logging in uncaught-exceptionhandler doesn't go through log4j

[ https://issues.apache.org/jira/browse/KAFKA-12774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443709#comment-17443709 ] David Jacot commented on KAFKA-12774: - Moving to the next release as we are past the 3.1 release

[jira] [Updated] (KAFKA-12699) Streams no longer overrides the java default uncaught exception handler

[ https://issues.apache.org/jira/browse/KAFKA-12699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12699: Fix Version/s: 3.2.0 (was: 3.1.0) > Streams no longer overrides the java

[jira] [Updated] (KAFKA-12774) kafka-streams 2.8: logging in uncaught-exceptionhandler doesn't go through log4j

[ https://issues.apache.org/jira/browse/KAFKA-12774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12774: Fix Version/s: 3.2.0 (was: 3.1.0) > kafka-streams 2.8: logging in

[jira] [Commented] (KAFKA-12283) Flaky Test RebalanceSourceConnectorsIntegrationTest#testMultipleWorkersRejoining

[ https://issues.apache.org/jira/browse/KAFKA-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443712#comment-17443712 ] David Jacot commented on KAFKA-12283: - Moving to the next release as we are past the 3.1 release

[jira] [Commented] (KAFKA-12699) Streams no longer overrides the java default uncaught exception handler

[ https://issues.apache.org/jira/browse/KAFKA-12699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443708#comment-17443708 ] David Jacot commented on KAFKA-12699: - Moving to the next release as we are past the 3.1 release

[jira] [Updated] (KAFKA-7435) Consider standardizing the config object pattern on interface/implementation.

[ https://issues.apache.org/jira/browse/KAFKA-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-7435: --- Fix Version/s: 3.2.0 (was: 3.1.0) > Consider standardizing the config object

[jira] [Commented] (KAFKA-7435) Consider standardizing the config object pattern on interface/implementation.

[ https://issues.apache.org/jira/browse/KAFKA-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443705#comment-17443705 ] David Jacot commented on KAFKA-7435: Moving to the next release as we are past the 3.1 release code

[jira] [Commented] (KAFKA-12712) KRaft: Missing controller.quorom.voters config not properly handled

[ https://issues.apache.org/jira/browse/KAFKA-12712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443704#comment-17443704 ] David Jacot commented on KAFKA-12712: - Moving to the next release as we are past the 3.1 release

[jira] [Updated] (KAFKA-12644) Add Missing Class-Level Javadoc to Descendants of org.apache.kafka.common.errors.ApiException

[ https://issues.apache.org/jira/browse/KAFKA-12644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12644: Fix Version/s: 3.2.0 (was: 3.1.0) > Add Missing Class-Level Javadoc to

[jira] [Commented] (KAFKA-12644) Add Missing Class-Level Javadoc to Descendants of org.apache.kafka.common.errors.ApiException

[ https://issues.apache.org/jira/browse/KAFKA-12644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443703#comment-17443703 ] David Jacot commented on KAFKA-12644: - Moving to the next release as we are past the 3.1 release

[jira] [Updated] (KAFKA-12781) Improve the endOffsets accuracy in TaskMetadata

[ https://issues.apache.org/jira/browse/KAFKA-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12781: Fix Version/s: 3.2.0 (was: 3.1.0) > Improve the endOffsets accuracy in

<    1   2   3   4   5   6   7   8   9   >