[jira] [Resolved] (KAFKA-15510) Follower's lastFetchedEpoch wrongly set when fetch response has no record

[ https://issues.apache.org/jira/browse/KAFKA-15510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-15510. Fix Version/s: 3.7.0 Resolution: Fixed > Follower's lastFetchedEpoch wrongly set

[jira] [Commented] (KAFKA-15510) Follower's lastFetchedEpoch wrongly set when fetch response has no record

[ https://issues.apache.org/jira/browse/KAFKA-15510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770051#comment-17770051 ] Rajini Sivaram commented on KAFKA-15510: This does not currently impact truncation in followers,

[jira] [Resolved] (KAFKA-15117) SslTransportLayerTest.testValidEndpointIdentificationCN fails with Java 20 & 21

[ https://issues.apache.org/jira/browse/KAFKA-15117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-15117. Reviewer: Rajini Sivaram Resolution: Fixed >

[jira] [Resolved] (KAFKA-14891) Fix rack-aware range assignor to improve rack-awareness with co-partitioning

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

[jira] [Created] (KAFKA-14891) Fix rack-aware range assignor to improve rack-awareness with co-partitioning

Rajini Sivaram created KAFKA-14891: -- Summary: Fix rack-aware range assignor to improve rack-awareness with co-partitioning Key: KAFKA-14891 URL: https://issues.apache.org/jira/browse/KAFKA-14891

[jira] [Resolved] (KAFKA-14450) Rack-aware partition assignment for consumers (KIP-881)

[ https://issues.apache.org/jira/browse/KAFKA-14450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-14450. Resolution: Fixed > Rack-aware partition assignment for consumers (KIP-881) >

[jira] [Resolved] (KAFKA-14452) Make sticky assignors rack-aware if consumer racks are configured.

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

[jira] [Resolved] (KAFKA-14867) Trigger rebalance when replica racks change if client.rack is configured

[ https://issues.apache.org/jira/browse/KAFKA-14867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-14867. Reviewer: David Jacot Resolution: Fixed > Trigger rebalance when replica racks

[jira] [Created] (KAFKA-14867) Trigger rebalance when replica racks change if client.rack is configured

Rajini Sivaram created KAFKA-14867: -- Summary: Trigger rebalance when replica racks change if client.rack is configured Key: KAFKA-14867 URL: https://issues.apache.org/jira/browse/KAFKA-14867

[jira] [Resolved] (KAFKA-14770) Allow dynamic keystore update for brokers if string representation of DN matches even if canonical DNs don't match

[ https://issues.apache.org/jira/browse/KAFKA-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-14770. Reviewer: Manikumar Resolution: Fixed > Allow dynamic keystore update for brokers

[jira] [Resolved] (KAFKA-14451) Make range assignor rack-aware if consumer racks are configured

[ https://issues.apache.org/jira/browse/KAFKA-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-14451. Fix Version/s: 3.5.0 Reviewer: David Jacot Resolution: Fixed > Make range

[jira] [Created] (KAFKA-14770) Allow dynamic keystore update for brokers if string representation of DN matches even if canonical DNs don't match

Rajini Sivaram created KAFKA-14770: -- Summary: Allow dynamic keystore update for brokers if string representation of DN matches even if canonical DNs don't match Key: KAFKA-14770 URL:

[jira] [Resolved] (KAFKA-14676) Token endpoint URL used for OIDC cannot be set on the JAAS config

[ https://issues.apache.org/jira/browse/KAFKA-14676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-14676. Fix Version/s: 3.5.0 3.4.1 3.3.3 Reviewer:

[jira] [Created] (KAFKA-14676) Token endpoint URL used for OIDC cannot be set on the JAAS config

Rajini Sivaram created KAFKA-14676: -- Summary: Token endpoint URL used for OIDC cannot be set on the JAAS config Key: KAFKA-14676 URL: https://issues.apache.org/jira/browse/KAFKA-14676 Project: Kafka

[jira] [Resolved] (KAFKA-14352) Support rack-aware partition assignment for Kafka consumers

[ https://issues.apache.org/jira/browse/KAFKA-14352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-14352. Reviewer: David Jacot Resolution: Fixed This includes protocol changes for

[jira] [Created] (KAFKA-14452) Make sticky assignors rack-aware if consumer racks are configured.

Rajini Sivaram created KAFKA-14452: -- Summary: Make sticky assignors rack-aware if consumer racks are configured. Key: KAFKA-14452 URL: https://issues.apache.org/jira/browse/KAFKA-14452 Project:

[jira] [Created] (KAFKA-14451) Make range assignor rack-aware if consumer racks are configured

Rajini Sivaram created KAFKA-14451: -- Summary: Make range assignor rack-aware if consumer racks are configured Key: KAFKA-14451 URL: https://issues.apache.org/jira/browse/KAFKA-14451 Project: Kafka

[jira] [Updated] (KAFKA-14352) Support rack-aware partition assignment for Kafka consumers

[ https://issues.apache.org/jira/browse/KAFKA-14352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-14352: --- Parent: KAFKA-14450 Issue Type: Sub-task (was: New Feature) > Support rack-aware

[jira] [Created] (KAFKA-14450) Rack-aware partition assignment for consumers (KIP-881)

Rajini Sivaram created KAFKA-14450: -- Summary: Rack-aware partition assignment for consumers (KIP-881) Key: KAFKA-14450 URL: https://issues.apache.org/jira/browse/KAFKA-14450 Project: Kafka

[jira] [Created] (KAFKA-14352) Support rack-aware partition assignment for Kafka consumers

Rajini Sivaram created KAFKA-14352: -- Summary: Support rack-aware partition assignment for Kafka consumers Key: KAFKA-14352 URL: https://issues.apache.org/jira/browse/KAFKA-14352 Project: Kafka

[jira] [Resolved] (KAFKA-13559) The broker's ProduceResponse may be delayed for 300ms

[ https://issues.apache.org/jira/browse/KAFKA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13559. Fix Version/s: 3.4.0 Reviewer: Rajini Sivaram Resolution: Fixed > The

[jira] [Resolved] (KAFKA-13539) Improve propagation and processing of SSL handshake failures

[ https://issues.apache.org/jira/browse/KAFKA-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13539. Reviewer: Manikumar Resolution: Fixed > Improve propagation and processing of SSL

[jira] [Created] (KAFKA-13539) Improve propagation and processing of SSL handshake failures

Rajini Sivaram created KAFKA-13539: -- Summary: Improve propagation and processing of SSL handshake failures Key: KAFKA-13539 URL: https://issues.apache.org/jira/browse/KAFKA-13539 Project: Kafka

[jira] [Resolved] (KAFKA-13461) KafkaController stops functioning as active controller after ZooKeeperClient auth failure

[ https://issues.apache.org/jira/browse/KAFKA-13461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13461. Fix Version/s: 3.1.0 3.0.1 Reviewer: Jun Rao

[jira] [Commented] (KAFKA-13405) Kafka Streams restore-consumer fails to refresh broker IPs after upgrading Kafka cluster

[ https://issues.apache.org/jira/browse/KAFKA-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446375#comment-17446375 ] Rajini Sivaram commented on KAFKA-13405: I am not familiar with the specific restore consumer

[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=17444517#comment-17444517 ] Rajini Sivaram commented on KAFKA-13422: Yes, I remember now, we do take the first entry from

[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=1738#comment-1738 ] Rajini Sivaram commented on KAFKA-13422: [~RivenSun] We should have probably added that check

[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=1710#comment-1710 ] Rajini Sivaram commented on KAFKA-13422: [~RivenSun] Producers, consumers and other clients

[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=17444396#comment-17444396 ] Rajini Sivaram commented on KAFKA-13422: [~RivenSun] The recommended way for configuring SASL

[jira] [Commented] (KAFKA-13293) Support client reload of PEM certificates

[ https://issues.apache.org/jira/browse/KAFKA-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414263#comment-17414263 ] Rajini Sivaram commented on KAFKA-13293: [~teabot] Sorry, I should have said `recreates

[jira] [Commented] (KAFKA-13293) Support client reload of PEM certificates

[ https://issues.apache.org/jira/browse/KAFKA-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414217#comment-17414217 ] Rajini Sivaram commented on KAFKA-13293: [~teabot] Yes, agree that it will be useful to support

[jira] [Commented] (KAFKA-12751) ISRs remain in in-flight state if proposed state is same as actual state

[ https://issues.apache.org/jira/browse/KAFKA-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414212#comment-17414212 ] Rajini Sivaram commented on KAFKA-12751: The bug only happens in an unusual case where the

[jira] [Commented] (KAFKA-13293) Support client reload of PEM certificates

[ https://issues.apache.org/jira/browse/KAFKA-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414137#comment-17414137 ] Rajini Sivaram commented on KAFKA-13293: [~teabot] Which client (and configs) do you use to

[jira] [Comment Edited] (KAFKA-10338) Support PEM format for SSL certificates and private key

[ https://issues.apache.org/jira/browse/KAFKA-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413395#comment-17413395 ] Rajini Sivaram edited comment on KAFKA-10338 at 9/10/21, 9:27 PM: --

[jira] [Commented] (KAFKA-10338) Support PEM format for SSL certificates and private key

[ https://issues.apache.org/jira/browse/KAFKA-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413395#comment-17413395 ] Rajini Sivaram commented on KAFKA-10338: [~teabot] We currently don't have a way of updating PEM

[jira] [Updated] (KAFKA-13277) Serialization of long tagged string in request/response throws BufferOverflowException

[ https://issues.apache.org/jira/browse/KAFKA-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-13277: --- Fix Version/s: 2.7.2 > Serialization of long tagged string in request/response throws >

[jira] [Updated] (KAFKA-13277) Serialization of long tagged string in request/response throws BufferOverflowException

[ https://issues.apache.org/jira/browse/KAFKA-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-13277: --- Affects Version/s: 2.4.1 2.5.1 2.8.0

[jira] [Updated] (KAFKA-13277) Serialization of long tagged string in request/response throws BufferOverflowException

[ https://issues.apache.org/jira/browse/KAFKA-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-13277: --- Fix Version/s: 2.8.1 > Serialization of long tagged string in request/response throws >

[jira] [Updated] (KAFKA-13277) Serialization of long tagged string in request/response throws BufferOverflowException

[ https://issues.apache.org/jira/browse/KAFKA-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-13277: --- Fix Version/s: (was: 3.0.1) 3.0.0 > Serialization of long tagged

[jira] [Updated] (KAFKA-13277) Serialization of long tagged string in request/response throws BufferOverflowException

[ https://issues.apache.org/jira/browse/KAFKA-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-13277: --- Priority: Blocker (was: Major) > Serialization of long tagged string in request/response

[jira] [Commented] (KAFKA-13277) Serialization of long tagged string in request/response throws BufferOverflowException

[ https://issues.apache.org/jira/browse/KAFKA-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411311#comment-17411311 ] Rajini Sivaram commented on KAFKA-13277: [~ijuma] Yes, it will be good include in 3.0. >

[jira] [Created] (KAFKA-13277) Serialization of long tagged string in request/response throws BufferOverflowException

Rajini Sivaram created KAFKA-13277: -- Summary: Serialization of long tagged string in request/response throws BufferOverflowException Key: KAFKA-13277 URL: https://issues.apache.org/jira/browse/KAFKA-13277

[jira] [Resolved] (KAFKA-10774) Support Describe topic using topic IDs

[ https://issues.apache.org/jira/browse/KAFKA-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-10774. Fix Version/s: 3.1.0 Reviewer: Rajini Sivaram Resolution: Fixed > Support

[jira] [Resolved] (KAFKA-13207) Replica fetcher should not update partition state on diverging epoch if partition removed from fetcher

[ https://issues.apache.org/jira/browse/KAFKA-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13207. Resolution: Fixed > Replica fetcher should not update partition state on diverging epoch

[jira] [Created] (KAFKA-13207) Replica fetcher should not update partition state on diverging epoch if partition removed from fetcher

Rajini Sivaram created KAFKA-13207: -- Summary: Replica fetcher should not update partition state on diverging epoch if partition removed from fetcher Key: KAFKA-13207 URL:

[jira] [Resolved] (KAFKA-13141) Leader should not update follower fetch offset if diverging epoch is present

[ https://issues.apache.org/jira/browse/KAFKA-13141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13141. Reviewer: Jason Gustafson Resolution: Fixed > Leader should not update follower

[jira] [Resolved] (KAFKA-13026) Idempotent producer (KAFKA-10619) follow-up testings

[ https://issues.apache.org/jira/browse/KAFKA-13026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13026. Fix Version/s: 3.0.0 Reviewer: Rajini Sivaram Resolution: Fixed >

[jira] [Assigned] (KAFKA-13026) Idempotent producer (KAFKA-10619) follow-up testings

[ https://issues.apache.org/jira/browse/KAFKA-13026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-13026: -- Assignee: Cheng Tan > Idempotent producer (KAFKA-10619) follow-up testings >

[jira] [Created] (KAFKA-13043) Add Admin API for batched offset fetch requests (KIP-709)

Rajini Sivaram created KAFKA-13043: -- Summary: Add Admin API for batched offset fetch requests (KIP-709) Key: KAFKA-13043 URL: https://issues.apache.org/jira/browse/KAFKA-13043 Project: Kafka

[jira] [Resolved] (KAFKA-12234) Extend OffsetFetch requests to accept multiple group ids.

[ https://issues.apache.org/jira/browse/KAFKA-12234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12234. Reviewer: Rajini Sivaram Resolution: Fixed > Extend OffsetFetch requests to accept

[jira] [Resolved] (KAFKA-13029) FindCoordinators batching can break consumers during rolling upgrade

[ https://issues.apache.org/jira/browse/KAFKA-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-13029. Resolution: Fixed > FindCoordinators batching can break consumers during rolling upgrade

[jira] [Commented] (KAFKA-13029) FindCoordinators batching can break consumers during rolling upgrade

[ https://issues.apache.org/jira/browse/KAFKA-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373991#comment-17373991 ] Rajini Sivaram commented on KAFKA-13029: [~mimaison] [~dajac]  Consumer and transaction

[jira] [Created] (KAFKA-13029) FindCoordinators batching can break consumers during rolling upgrade

Rajini Sivaram created KAFKA-13029: -- Summary: FindCoordinators batching can break consumers during rolling upgrade Key: KAFKA-13029 URL: https://issues.apache.org/jira/browse/KAFKA-13029 Project:

[jira] [Updated] (KAFKA-12996) OffsetOutOfRange not handled correctly for diverging epochs when fetch offset less than leader start offset

[ https://issues.apache.org/jira/browse/KAFKA-12996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-12996: --- Fix Version/s: 2.7.2 Affects Version/s: 2.7.1 > OffsetOutOfRange not handled

[jira] [Resolved] (KAFKA-12996) OffsetOutOfRange not handled correctly for diverging epochs when fetch offset less than leader start offset

[ https://issues.apache.org/jira/browse/KAFKA-12996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12996. Reviewer: Guozhang Wang Resolution: Fixed > OffsetOutOfRange not handled correctly

[jira] [Created] (KAFKA-12996) OffsetOutOfRange not handled correctly for diverging epochs when fetch offset less than leader start offset

Rajini Sivaram created KAFKA-12996: -- Summary: OffsetOutOfRange not handled correctly for diverging epochs when fetch offset less than leader start offset Key: KAFKA-12996 URL:

[jira] [Commented] (KAFKA-12948) NetworkClient.close(node) with node in connecting state makes NetworkClient unusable

[ https://issues.apache.org/jira/browse/KAFKA-12948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363490#comment-17363490 ] Rajini Sivaram commented on KAFKA-12948: Yes, it was due to the changes from

[jira] [Resolved] (KAFKA-12948) NetworkClient.close(node) with node in connecting state makes NetworkClient unusable

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

[jira] [Created] (KAFKA-12948) NetworkClient.close(node) with node in connecting state makes NetworkClient unusable

Rajini Sivaram created KAFKA-12948: -- Summary: NetworkClient.close(node) with node in connecting state makes NetworkClient unusable Key: KAFKA-12948 URL: https://issues.apache.org/jira/browse/KAFKA-12948

[jira] [Resolved] (KAFKA-12867) Trogdor ConsumeBenchWorker quits prematurely with maxMessages config

[ https://issues.apache.org/jira/browse/KAFKA-12867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12867. Fix Version/s: 3.0.0 Reviewer: Rajini Sivaram Resolution: Fixed > Trogdor

[jira] [Assigned] (KAFKA-12867) Trogdor ConsumeBenchWorker quits prematurely with maxMessages config

[ https://issues.apache.org/jira/browse/KAFKA-12867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-12867: -- Assignee: Kowshik Prakasam > Trogdor ConsumeBenchWorker quits prematurely with

[jira] [Resolved] (KAFKA-12751) ISRs remain in in-flight state if proposed state is same as actual state

[ https://issues.apache.org/jira/browse/KAFKA-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12751. Reviewer: David Arthur Resolution: Fixed > ISRs remain in in-flight state if

[jira] [Updated] (KAFKA-12730) A single Kerberos login failure fails all future connections from Java 9 onwards

[ https://issues.apache.org/jira/browse/KAFKA-12730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-12730: --- Fix Version/s: 2.8.1 2.7.2 2.6.3

[jira] [Updated] (KAFKA-10727) Kafka clients throw AuthenticationException during Kerberos re-login

[ https://issues.apache.org/jira/browse/KAFKA-10727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-10727: --- Fix Version/s: 2.7.2 2.6.3 2.5.2 > Kafka clients

[jira] [Created] (KAFKA-12751) ISRs remain in in-flight state if proposed state is same as actual state

Rajini Sivaram created KAFKA-12751: -- Summary: ISRs remain in in-flight state if proposed state is same as actual state Key: KAFKA-12751 URL: https://issues.apache.org/jira/browse/KAFKA-12751

[jira] [Resolved] (KAFKA-12730) A single Kerberos login failure fails all future connections from Java 9 onwards

[ https://issues.apache.org/jira/browse/KAFKA-12730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12730. Reviewer: Manikumar Resolution: Fixed > A single Kerberos login failure fails all

[jira] [Created] (KAFKA-12730) A single Kerberos login failure fails all future connections from Java 9 onwards

Rajini Sivaram created KAFKA-12730: -- Summary: A single Kerberos login failure fails all future connections from Java 9 onwards Key: KAFKA-12730 URL: https://issues.apache.org/jira/browse/KAFKA-12730

[jira] [Commented] (KAFKA-12598) Remove deprecated --zookeeper in ConfigCommand

[ https://issues.apache.org/jira/browse/KAFKA-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320471#comment-17320471 ] Rajini Sivaram commented on KAFKA-12598: [~cmccabe] [~hachikuji] Have we figured out how/when to

[jira] [Resolved] (KAFKA-12479) Combine partition offset requests into single request in ConsumerGroupCommand

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

[jira] [Resolved] (KAFKA-12268) System tests broken because consumer returns early without records

[ https://issues.apache.org/jira/browse/KAFKA-12268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12268. Resolution: Fixed > System tests broken because consumer returns early without records >

[jira] [Assigned] (KAFKA-12268) System tests broken because consumer returns early without records

[ https://issues.apache.org/jira/browse/KAFKA-12268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-12268: -- Assignee: John Roesler (was: Rajini Sivaram) > System tests broken because consumer

[jira] [Resolved] (KAFKA-12330) FetchSessionCache may cause starvation for partitions when FetchResponse is full

[ https://issues.apache.org/jira/browse/KAFKA-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12330. Fix Version/s: 3.0.0 Resolution: Fixed > FetchSessionCache may cause starvation

[jira] [Resolved] (KAFKA-12427) Broker does not close muted idle connections with buffered data

[ https://issues.apache.org/jira/browse/KAFKA-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-12427. Fix Version/s: 3.0.0 Reviewer: Rajini Sivaram Resolution: Fixed > Broker

[jira] [Created] (KAFKA-12479) Combine partition offset requests into single request in ConsumerGroupCommand

Rajini Sivaram created KAFKA-12479: -- Summary: Combine partition offset requests into single request in ConsumerGroupCommand Key: KAFKA-12479 URL: https://issues.apache.org/jira/browse/KAFKA-12479

[jira] [Commented] (KAFKA-12431) Fetch Request/Response without Topic information

[ https://issues.apache.org/jira/browse/KAFKA-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297989#comment-17297989 ] Rajini Sivaram commented on KAFKA-12431: I can't think of any changes in 2.5.x or 2.6.x that

[jira] [Updated] (KAFKA-12254) MirrorMaker 2.0 creates destination topic with default configs

[ https://issues.apache.org/jira/browse/KAFKA-12254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-12254: --- Fix Version/s: (was: 3.0.0) > MirrorMaker 2.0 creates destination topic with default

[jira] [Resolved] (KAFKA-10700) Support mutual TLS authentication for SASL_SSL listeners

[ https://issues.apache.org/jira/browse/KAFKA-10700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-10700. Reviewer: David Jacot Resolution: Fixed > Support mutual TLS authentication for

[jira] [Created] (KAFKA-12268) System tests broken because consumer returns early without records

Rajini Sivaram created KAFKA-12268: -- Summary: System tests broken because consumer returns early without records Key: KAFKA-12268 URL: https://issues.apache.org/jira/browse/KAFKA-12268 Project:

[jira] [Updated] (KAFKA-10798) Failed authentication delay doesn't work with some SASL authentication failures

[ https://issues.apache.org/jira/browse/KAFKA-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-10798: --- Fix Version/s: 2.6.2 2.7.1 > Failed authentication delay doesn't work

[jira] [Resolved] (KAFKA-10798) Failed authentication delay doesn't work with some SASL authentication failures

[ https://issues.apache.org/jira/browse/KAFKA-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-10798. Reviewer: Manikumar Resolution: Fixed > Failed authentication delay doesn't work

[jira] [Resolved] (KAFKA-10554) Perform follower truncation based on epoch offsets returned in Fetch response

[ https://issues.apache.org/jira/browse/KAFKA-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-10554. Reviewer: Jason Gustafson Resolution: Fixed > Perform follower truncation based on

[jira] [Created] (KAFKA-10798) Failed authentication delay doesn't work with some SASL authentication failures

Rajini Sivaram created KAFKA-10798: -- Summary: Failed authentication delay doesn't work with some SASL authentication failures Key: KAFKA-10798 URL: https://issues.apache.org/jira/browse/KAFKA-10798

[jira] [Resolved] (KAFKA-10727) Kafka clients throw AuthenticationException during Kerberos re-login

[ https://issues.apache.org/jira/browse/KAFKA-10727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-10727. Fix Version/s: 2.8.0 Reviewer: Manikumar Resolution: Fixed > Kafka

[jira] [Created] (KAFKA-10727) Kafka clients throw AuthenticationException during Kerberos re-login

Rajini Sivaram created KAFKA-10727: -- Summary: Kafka clients throw AuthenticationException during Kerberos re-login Key: KAFKA-10727 URL: https://issues.apache.org/jira/browse/KAFKA-10727 Project:

[jira] [Created] (KAFKA-10700) Support mutual TLS authentication for SASL_SSL listeners

Rajini Sivaram created KAFKA-10700: -- Summary: Support mutual TLS authentication for SASL_SSL listeners Key: KAFKA-10700 URL: https://issues.apache.org/jira/browse/KAFKA-10700 Project: Kafka

[jira] [Resolved] (KAFKA-7987) a broker's ZK session may die on transient auth failure

[ https://issues.apache.org/jira/browse/KAFKA-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7987. --- Fix Version/s: 2.8.0 Reviewer: Jun Rao Resolution: Fixed > a broker's ZK

[jira] [Commented] (KAFKA-7987) a broker's ZK session may die on transient auth failure

[ https://issues.apache.org/jira/browse/KAFKA-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221756#comment-17221756 ] Rajini Sivaram commented on KAFKA-7987: --- [~junrao]Thank you! I will follow up on the PR. > a

[jira] [Updated] (KAFKA-7987) a broker's ZK session may die on transient auth failure

[ https://issues.apache.org/jira/browse/KAFKA-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-7987: -- Issue Type: Bug (was: Improvement) Priority: Critical (was: Major) > a broker's ZK

[jira] [Commented] (KAFKA-7987) a broker's ZK session may die on transient auth failure

[ https://issues.apache.org/jira/browse/KAFKA-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221328#comment-17221328 ] Rajini Sivaram commented on KAFKA-7987: --- [~junrao] This is still an open issue for all versions of

[jira] [Created] (KAFKA-10626) Add support for max.in.flight.requests.per.connection behaviour in MockClient

Rajini Sivaram created KAFKA-10626: -- Summary: Add support for max.in.flight.requests.per.connection behaviour in MockClient Key: KAFKA-10626 URL: https://issues.apache.org/jira/browse/KAFKA-10626

[jira] [Updated] (KAFKA-10233) KafkaConsumer polls in a tight loop if group is not authorized

[ https://issues.apache.org/jira/browse/KAFKA-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-10233: --- Fix Version/s: (was: 2.7.0) 2.8.0 > KafkaConsumer polls in a tight

[jira] [Commented] (KAFKA-10520) InitProducerId may be blocked if least loaded node is not ready to send

[ https://issues.apache.org/jira/browse/KAFKA-10520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17209737#comment-17209737 ] Rajini Sivaram commented on KAFKA-10520: [~ableegoldman] Yes, will try and get this done in time

[jira] [Assigned] (KAFKA-10520) InitProducerId may be blocked if least loaded node is not ready to send

[ https://issues.apache.org/jira/browse/KAFKA-10520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-10520: -- Assignee: Rajini Sivaram > InitProducerId may be blocked if least loaded node is not

[jira] [Resolved] (KAFKA-9497) Brokers start up even if SASL provider is not loaded and throw NPE when clients connect

[ https://issues.apache.org/jira/browse/KAFKA-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-9497. --- Resolution: Duplicate > Brokers start up even if SASL provider is not loaded and throw NPE

[jira] [Assigned] (KAFKA-9497) Brokers start up even if SASL provider is not loaded and throw NPE when clients connect

[ https://issues.apache.org/jira/browse/KAFKA-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-9497: - Assignee: Ron Dagostino (was: Rajini Sivaram) > Brokers start up even if SASL provider

[jira] [Updated] (KAFKA-10338) Support PEM format for SSL certificates and private key

[ https://issues.apache.org/jira/browse/KAFKA-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-10338: --- Description: We currently support only file-based JKS/PKCS12 format for SSL key stores and

[jira] [Resolved] (KAFKA-10338) Support PEM format for SSL certificates and private key

[ https://issues.apache.org/jira/browse/KAFKA-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-10338. Fix Version/s: 2.7.0 Reviewer: Manikumar Resolution: Fixed > Support PEM

[jira] [Created] (KAFKA-10554) Perform follower truncation based on epoch offsets returned in Fetch response

Rajini Sivaram created KAFKA-10554: -- Summary: Perform follower truncation based on epoch offsets returned in Fetch response Key: KAFKA-10554 URL: https://issues.apache.org/jira/browse/KAFKA-10554

[jira] [Updated] (KAFKA-10520) InitProducerId may be blocked if least loaded node is not ready to send

[ https://issues.apache.org/jira/browse/KAFKA-10520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-10520: --- Description: >From the logs of a failing producer that shows InitProducerId timing out

[jira] [Created] (KAFKA-10520) InitProducerId may be blocked if least loaded node is not ready to send

Rajini Sivaram created KAFKA-10520: -- Summary: InitProducerId may be blocked if least loaded node is not ready to send Key: KAFKA-10520 URL: https://issues.apache.org/jira/browse/KAFKA-10520 Project:

  1   2   3   4   5   6   7   8   9   >