[jira] [Commented] (KAFKA-9990) Supporting transactions in tiered storage

[ https://issues.apache.org/jira/browse/KAFKA-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437348#comment-17437348 ] David Jacot commented on KAFKA-9990: Feature freeze for AK 3.1 has passed. Pushing to

[jira] [Commented] (KAFKA-12878) Support --bootstrap-server kafka-streams-application-reset

[ https://issues.apache.org/jira/browse/KAFKA-12878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437344#comment-17437344 ] David Jacot commented on KAFKA-12878: - I wasn't able to find a KIP for this feature.

[jira] [Updated] (KAFKA-12878) Support --bootstrap-server kafka-streams-application-reset

[ https://issues.apache.org/jira/browse/KAFKA-12878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12878: Fix Version/s: (was: 3.1.0) 3.2.0 > Support --bootstrap-server kafka-stream

[jira] [Commented] (KAFKA-13331) Slow reassignments in 2.8 because of large number of UpdateMetadataResponseReceived(UpdateMetadataResponseData(errorCode=0),) Events

[ https://issues.apache.org/jira/browse/KAFKA-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437343#comment-17437343 ] David Jacot commented on KAFKA-13331: - Moving the target release to 3.2. > Slow rea

[jira] [Updated] (KAFKA-13331) Slow reassignments in 2.8 because of large number of UpdateMetadataResponseReceived(UpdateMetadataResponseData(errorCode=0),) Events

[ https://issues.apache.org/jira/browse/KAFKA-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13331: Fix Version/s: (was: 3.1.0) 3.2.0 > Slow reassignments in 2.8 because of la

[jira] [Commented] (KAFKA-12291) Fix Ignored Upgrade Tests in streams_upgrade_test.py: test_upgrade_downgrade_brokers

[ https://issues.apache.org/jira/browse/KAFKA-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437342#comment-17437342 ] David Jacot commented on KAFKA-12291: - [~cadonna] Is this issue really a blocker? It

[jira] [Commented] (KAFKA-12487) Sink connectors do not work with the cooperative consumer rebalance protocol

[ https://issues.apache.org/jira/browse/KAFKA-12487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437340#comment-17437340 ] David Jacot commented on KAFKA-12487: - [~ChrisEgerton] Do we still plan to get this

[jira] [Commented] (KAFKA-9366) Upgrade log4j to log4j2

[ https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437337#comment-17437337 ] David Jacot commented on KAFKA-9366: Moved the target release to the next one as the

[jira] [Updated] (KAFKA-7632) Support Compression Level

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

[jira] [Commented] (KAFKA-7632) Support Compression Level

[ https://issues.apache.org/jira/browse/KAFKA-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437339#comment-17437339 ] David Jacot commented on KAFKA-7632: Moved the target release to 3.2.0. > Support Co

[jira] [Commented] (KAFKA-7739) Kafka Tiered Storage

[ https://issues.apache.org/jira/browse/KAFKA-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437338#comment-17437338 ] David Jacot commented on KAFKA-7739: Moved the target version to 3.2.0 since there ar

[jira] [Updated] (KAFKA-7739) Kafka Tiered Storage

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

[jira] [Updated] (KAFKA-9366) Upgrade log4j to log4j2

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

[jira] [Commented] (KAFKA-10000) Atomic commit of source connector records and offsets

[ https://issues.apache.org/jira/browse/KAFKA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437336#comment-17437336 ] David Jacot commented on KAFKA-1: - Moved the target release to the next one. >

[jira] [Updated] (KAFKA-6080) Transactional EoS for source connectors

[ https://issues.apache.org/jira/browse/KAFKA-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-6080: --- Fix Version/s: (was: 3.1.0) 3.2.0 > Transactional EoS for source connectors >

[jira] [Commented] (KAFKA-10733) Enforce exception thrown for KafkaProducer txn APIs

[ https://issues.apache.org/jira/browse/KAFKA-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437335#comment-17437335 ] David Jacot commented on KAFKA-10733: - Moved the target release to the next one. >

[jira] [Updated] (KAFKA-6718) Rack Aware Stand-by Task Assignment for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-6718: --- Fix Version/s: (was: 3.1.0) 3.2.0 > Rack Aware Stand-by Task Assignment for Ka

[jira] [Commented] (KAFKA-6718) Rack Aware Stand-by Task Assignment for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437334#comment-17437334 ] David Jacot commented on KAFKA-6718: The main PR for this feature hasn't been approve

[jira] [Updated] (KAFKA-10000) Atomic commit of source connector records and offsets

[ https://issues.apache.org/jira/browse/KAFKA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-1: Fix Version/s: (was: 3.1.0) 3.2.0 > Atomic commit of source connector recor

[jira] [Updated] (KAFKA-10733) Enforce exception thrown for KafkaProducer txn APIs

[ https://issues.apache.org/jira/browse/KAFKA-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-10733: Fix Version/s: (was: 3.1.0) 3.2.0 > Enforce exception thrown for KafkaProdu

[jira] [Updated] (KAFKA-13394) Topic IDs should be removed from PartitionFetchState if they are no longer sent by the controller

[ https://issues.apache.org/jira/browse/KAFKA-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13394: Priority: Blocker (was: Major) > Topic IDs should be removed from PartitionFetchState if they are

[jira] [Updated] (KAFKA-13394) Topic IDs should be removed from PartitionFetchState if they are no longer sent by the controller

[ https://issues.apache.org/jira/browse/KAFKA-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13394: Fix Version/s: 3.1.0 > Topic IDs should be removed from PartitionFetchState if they are no longer

[jira] [Updated] (KAFKA-13111) Re-evaluate Fetch Sessions when using topic IDs

[ https://issues.apache.org/jira/browse/KAFKA-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13111: Fix Version/s: 3.1.0 > Re-evaluate Fetch Sessions when using topic IDs > -

[jira] [Commented] (KAFKA-7632) Support Compression Level

[ https://issues.apache.org/jira/browse/KAFKA-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434195#comment-17434195 ] David Jacot commented on KAFKA-7632: I was reduced the priority. > Support Compressi

[jira] [Updated] (KAFKA-7632) Support Compression Level

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

[jira] [Updated] (KAFKA-13111) Re-evaluate Fetch Sessions when using topic IDs

[ https://issues.apache.org/jira/browse/KAFKA-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13111: Priority: Blocker (was: Major) > Re-evaluate Fetch Sessions when using topic IDs > --

[jira] [Resolved] (KAFKA-12882) Add ActiveBrokerCount and FencedBrokerCount metrics (KIP-748)

[ https://issues.apache.org/jira/browse/KAFKA-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-12882. - Fix Version/s: 3.1.0 Resolution: Fixed > Add ActiveBrokerCount and FencedBrokerCount metr

[jira] [Resolved] (KAFKA-13238) Add ActiveBrokerCount and FencedBrokerCount metrics to the KRaft controller (KIP-748)

[ https://issues.apache.org/jira/browse/KAFKA-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13238. - Fix Version/s: 3.1.0 Assignee: Ryan Dielhenn Resolution: Fixed > Add ActiveBroke

[jira] [Commented] (KAFKA-13238) Add ActiveBrokerCount and FencedBrokerCount metrics to the KRaft controller (KIP-748)

[ https://issues.apache.org/jira/browse/KAFKA-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433627#comment-17433627 ] David Jacot commented on KAFKA-13238: - This was addressed by https://github.com/apac

[jira] [Updated] (KAFKA-13381) Wrap all uncaught exceptions as StreamsException with TaskId field

[ https://issues.apache.org/jira/browse/KAFKA-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13381: Fix Version/s: 3.1.0 > Wrap all uncaught exceptions as StreamsException with TaskId field > --

[jira] [Commented] (KAFKA-13388) Kafka Producer has no timeout for nodes stuck in CHECKING_API_VERSIONS

[ https://issues.apache.org/jira/browse/KAFKA-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432563#comment-17432563 ] David Jacot commented on KAFKA-13388: - Interesting... It would be great if you could

[jira] [Commented] (KAFKA-13388) Kafka Producer has no timeout for nodes stuck in CHECKING_API_VERSIONS

[ https://issues.apache.org/jira/browse/KAFKA-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432238#comment-17432238 ] David Jacot commented on KAFKA-13388: - [~dhofftgt] Thanks for filing this issue. Whi

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

[ https://issues.apache.org/jira/browse/KAFKA-13043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13043: Fix Version/s: (was: 3.1.0) 3.2.0 > Add Admin API for batched offset fetch

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

[ https://issues.apache.org/jira/browse/KAFKA-13043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430444#comment-17430444 ] David Jacot commented on KAFKA-13043: - Moving this feature to 3.2.0 as [~skaundinya]

[jira] [Commented] (KAFKA-7632) Support Compression Level

[ https://issues.apache.org/jira/browse/KAFKA-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429860#comment-17429860 ] David Jacot commented on KAFKA-7632: [~dongjin] Why do we consider this issue as a bl

[jira] [Commented] (KAFKA-10733) Enforce exception thrown for KafkaProducer txn APIs

[ https://issues.apache.org/jira/browse/KAFKA-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429856#comment-17429856 ] David Jacot commented on KAFKA-10733: - [~bchen225242] Do we plan to get this on in 3

[jira] [Commented] (KAFKA-12473) Make the "cooperative-sticky, range" as the default assignor

[ https://issues.apache.org/jira/browse/KAFKA-12473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429853#comment-17429853 ] David Jacot commented on KAFKA-12473: - [~showuon] [~ableegoldman] I am triaging the

[jira] [Updated] (KAFKA-10000) Atomic commit of source connector records and offsets

[ https://issues.apache.org/jira/browse/KAFKA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-1: Fix Version/s: 3.1.0 > Atomic commit of source connector records and offsets > ---

[jira] [Updated] (KAFKA-6080) Transactional EoS for source connectors

[ https://issues.apache.org/jira/browse/KAFKA-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-6080: --- Fix Version/s: 3.1.0 > Transactional EoS for source connectors >

[jira] [Updated] (KAFKA-10357) Handle accidental deletion of repartition-topics as exceptional failure

[ https://issues.apache.org/jira/browse/KAFKA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-10357: Fix Version/s: (was: 3.1.0) 3.2.0 > Handle accidental deletion of repartiti

[jira] [Commented] (KAFKA-10357) Handle accidental deletion of repartition-topics as exceptional failure

[ https://issues.apache.org/jira/browse/KAFKA-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421234#comment-17421234 ] David Jacot commented on KAFKA-10357: - As [~cadonna] suggested on the dev mailing li

[jira] [Resolved] (KAFKA-13102) Topic IDs not propagated to metadata cache quickly enough for Fetch path

[ https://issues.apache.org/jira/browse/KAFKA-13102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13102. - Fix Version/s: 3.1.0 Reviewer: David Jacot Resolution: Fixed > Topic IDs not pro

[jira] [Commented] (KAFKA-13310) KafkaConsumer cannot jump out of the poll method, and the consumer is blocked in the ConsumerCoordinator method maybeAutoCommitOffsetsSync(Timer timer). Cpu and traffi

[ https://issues.apache.org/jira/browse/KAFKA-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417615#comment-17417615 ] David Jacot commented on KAFKA-13310: - [~RivenSun] Thanks for the bug report. The ti

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

David Jacot created KAFKA-13312: --- Summary: 'NetworkDegradeTest#test_rate' should wait until iperf server is listening Key: KAFKA-13312 URL: https://issues.apache.org/jira/browse/KAFKA-13312 Project: Kaf

[jira] [Assigned] (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 reassigned KAFKA-10712: --- Assignee: David Jacot > Update release scripts to Python3 > ---

[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: (was: 2.8.1) > kafka-streams 2.8: logging in uncaught-exceptionhandler doesn't

[jira] [Updated] (KAFKA-12622) Automate LICENSE file validation

[ https://issues.apache.org/jira/browse/KAFKA-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12622: Fix Version/s: (was: 2.8.1) 3.1.0 > Automate LICENSE file validation >

[jira] [Updated] (KAFKA-13164) State store is attached to wrong node in the Kafka Streams topology

[ https://issues.apache.org/jira/browse/KAFKA-13164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13164: Fix Version/s: (was: 2.8.1) > State store is attached to wrong node in the Kafka Streams topol

[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: (was: 2.8.1) > Add Missing Class-Level Javadoc to Descendants of > org.apache.

[jira] [Resolved] (KAFKA-13237) Add ActiveBrokerCount and FencedBrokerCount metrics to the ZK controller (KIP-748)

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

[jira] [Updated] (KAFKA-13266) `InitialFetchState` should be created after partition is removed from the fetchers

[ https://issues.apache.org/jira/browse/KAFKA-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13266: Description:  `ReplicationTest.test_replication_with_broker_failure` in KRaft mode sometimes fail

[jira] [Created] (KAFKA-13266) `InitialFetchState` should be created after partition is removed from the fetchers

David Jacot created KAFKA-13266: --- Summary: `InitialFetchState` should be created after partition is removed from the fetchers Key: KAFKA-13266 URL: https://issues.apache.org/jira/browse/KAFKA-13266 Proj

[jira] [Commented] (KAFKA-13258) AlterClientQuotas response does not include an error when it failed

[ https://issues.apache.org/jira/browse/KAFKA-13258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408011#comment-17408011 ] David Jacot commented on KAFKA-13258: - It seems that this one has been introduced by

[jira] [Commented] (KAFKA-13260) FindCoordinator errorCounts does not handle v4

[ https://issues.apache.org/jira/browse/KAFKA-13260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408003#comment-17408003 ] David Jacot commented on KAFKA-13260: - [~mimaison] Do this one affect 3.0 as well?

[jira] [Updated] (KAFKA-13092) Perf regression in LISR requests

[ https://issues.apache.org/jira/browse/KAFKA-13092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13092: Fix Version/s: 2.8.1 > Perf regression in LISR requests > > >

[jira] [Resolved] (KAFKA-13079) Forgotten Topics in Fetch Requests may incorrectly use topic IDs

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

[jira] [Commented] (KAFKA-12882) Add ActiveBrokerCount and FencedBrokerCount metrics (KIP-748)

[ https://issues.apache.org/jira/browse/KAFKA-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405630#comment-17405630 ] David Jacot commented on KAFKA-12882: - [~rdielhenn] I have split the ticket into two

[jira] [Assigned] (KAFKA-13238) Add ActiveBrokerCount and FencedBrokerCount metrics to the KRaft controller (KIP-748)

[ https://issues.apache.org/jira/browse/KAFKA-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13238: --- Assignee: (was: David Jacot) > Add ActiveBrokerCount and FencedBrokerCount metrics to t

[jira] [Created] (KAFKA-13238) Add ActiveBrokerCount and FencedBrokerCount metrics to the KRaft controller (KIP-748)

David Jacot created KAFKA-13238: --- Summary: Add ActiveBrokerCount and FencedBrokerCount metrics to the KRaft controller (KIP-748) Key: KAFKA-13238 URL: https://issues.apache.org/jira/browse/KAFKA-13238 P

[jira] [Created] (KAFKA-13237) Add ActiveBrokerCount and FencedBrokerCount metrics to the ZK controller (KIP-748)

David Jacot created KAFKA-13237: --- Summary: Add ActiveBrokerCount and FencedBrokerCount metrics to the ZK controller (KIP-748) Key: KAFKA-13237 URL: https://issues.apache.org/jira/browse/KAFKA-13237 Proj

[jira] [Updated] (KAFKA-12882) Add ActiveBrokerCount and FencedBrokerCount metrics (KIP-748)

[ https://issues.apache.org/jira/browse/KAFKA-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12882: Summary: Add ActiveBrokerCount and FencedBrokerCount metrics (KIP-748) (was: Add RegisteredBroker

[jira] [Resolved] (KAFKA-13231) `TransactionalMessageCopier.start_node` should wait until the process if fully started

[ https://issues.apache.org/jira/browse/KAFKA-13231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13231. - Fix Version/s: 3.0.1 2.8.1 3.1.0 Reviewer: Jason G

[jira] [Created] (KAFKA-13231) `TransactionalMessageCopier.start_node` should wait until the process if fully started

David Jacot created KAFKA-13231: --- Summary: `TransactionalMessageCopier.start_node` should wait until the process if fully started Key: KAFKA-13231 URL: https://issues.apache.org/jira/browse/KAFKA-13231

[jira] [Resolved] (KAFKA-13134) Heartbeat Request high lock contention

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

[jira] [Resolved] (KAFKA-12840) Removing `compact` cleaning on a topic should abort on-going compactions

[ https://issues.apache.org/jira/browse/KAFKA-12840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-12840. - Fix Version/s: 3.1.0 Reviewer: Jun Rao Resolution: Fixed > Removing `compact` cl

[jira] [Commented] (KAFKA-13081) Port sticky assignor fixes (KAFKA-12984) back to 2.8

[ https://issues.apache.org/jira/browse/KAFKA-13081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399566#comment-17399566 ] David Jacot commented on KAFKA-13081: - [~ableegoldman] [~showuon] This is the only r

[jira] [Updated] (KAFKA-12835) Topic IDs can mismatch on brokers (after interbroker protocol version update)

[ https://issues.apache.org/jira/browse/KAFKA-12835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12835: Fix Version/s: 2.8.1 > Topic IDs can mismatch on brokers (after interbroker protocol version updat

[jira] [Updated] (KAFKA-12890) Consumer group stuck in `CompletingRebalance`

[ https://issues.apache.org/jira/browse/KAFKA-12890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12890: Fix Version/s: 2.8.1 > Consumer group stuck in `CompletingRebalance` > ---

[jira] [Resolved] (KAFKA-13058) `AlterConsumerGroupOffsetsHandler` does not handle partition errors correctly.

[ https://issues.apache.org/jira/browse/KAFKA-13058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13058. - Reviewer: Rajini Sivaram Resolution: Fixed > `AlterConsumerGroupOffsetsHandler` does not h

[jira] [Created] (KAFKA-13103) Should group admin handlers consider REBALANCE_IN_PROGRESS and GROUP_AUTHORIZATION_FAILED as retryable errors?

David Jacot created KAFKA-13103: --- Summary: Should group admin handlers consider REBALANCE_IN_PROGRESS and GROUP_AUTHORIZATION_FAILED as retryable errors? Key: KAFKA-13103 URL: https://issues.apache.org/jira/browse/K

[jira] [Resolved] (KAFKA-13033) coordinator not available error should cause add into unmap list to do a new lookup

[ https://issues.apache.org/jira/browse/KAFKA-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13033. - Reviewer: David Jacot Resolution: Fixed > coordinator not available error should cause add

[jira] [Commented] (KAFKA-12896) Group rebalance loop caused by repeated group leader JoinGroups

[ https://issues.apache.org/jira/browse/KAFKA-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381083#comment-17381083 ] David Jacot commented on KAFKA-12896: - [~ableegoldman] With you two fixes, I think t

[jira] [Updated] (KAFKA-13033) coordinator not available error should cause add into unmap list to do a new lookup

[ https://issues.apache.org/jira/browse/KAFKA-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13033: Priority: Blocker (was: Major) > coordinator not available error should cause add into unmap list

[jira] [Updated] (KAFKA-13033) coordinator not available error should cause add into unmap list to do a new lookup

[ https://issues.apache.org/jira/browse/KAFKA-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13033: Attachment: Screenshot 2021-07-14 at 14.20.39.png > coordinator not available error should cause a

[jira] [Updated] (KAFKA-13033) coordinator not available error should cause add into unmap list to do a new lookup

[ https://issues.apache.org/jira/browse/KAFKA-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13033: Attachment: (was: Screenshot 2021-07-14 at 14.20.39.png) > coordinator not available error sho

[jira] [Updated] (KAFKA-13033) coordinator not available error should cause add into unmap list to do a new lookup

[ https://issues.apache.org/jira/browse/KAFKA-13033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13033: Fix Version/s: 3.0.0 > coordinator not available error should cause add into unmap list to do a ne

[jira] [Resolved] (KAFKA-10201) Update codebase to use more inclusive terms

[ https://issues.apache.org/jira/browse/KAFKA-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10201. - Resolution: Fixed > Update codebase to use more inclusive terms > --

[jira] [Resolved] (KAFKA-10589) Rename kafka-replica-verification CLI command line arguments for KIP-629

[ https://issues.apache.org/jira/browse/KAFKA-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10589. - Reviewer: David Jacot Resolution: Fixed > Rename kafka-replica-verification CLI command li

[jira] [Resolved] (KAFKA-10588) Rename kafka-console-consumer CLI command line arguments for KIP-629

[ https://issues.apache.org/jira/browse/KAFKA-10588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10588. - Reviewer: David Jacot Resolution: Fixed > Rename kafka-console-consumer CLI command line a

[jira] [Updated] (KAFKA-13058) `AlterConsumerGroupOffsetsHandler` does not handle partition errors correctly.

[ https://issues.apache.org/jira/browse/KAFKA-13058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13058: Fix Version/s: 3.0.0 > `AlterConsumerGroupOffsetsHandler` does not handle partition errors correct

[jira] [Created] (KAFKA-13058) `AlterConsumerGroupOffsetsHandler` does not handle partition errors correctly.

David Jacot created KAFKA-13058: --- Summary: `AlterConsumerGroupOffsetsHandler` does not handle partition errors correctly. Key: KAFKA-13058 URL: https://issues.apache.org/jira/browse/KAFKA-13058 Project:

[jira] [Resolved] (KAFKA-12981) Ensure LogSegment.maxTimestampSoFar and LogSegment.offsetOfMaxTimestampSoFar are read/updated in sync

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

[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&focusedCommentId=17373909#comment-17373909 ] David Jacot commented on KAFKA-13029: - For the consumer, I think a simpler version w

[jira] [Updated] (KAFKA-12981) Ensure LogSegment.maxTimestampSoFar and LogSegment.offsetOfMaxTimestampSoFar are read/updated in sync

[ https://issues.apache.org/jira/browse/KAFKA-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12981: Parent: (was: KAFKA-12541) Issue Type: Improvement (was: Sub-task) > Ensure LogSegmen

[jira] [Assigned] (KAFKA-12981) Ensure LogSegment.maxTimestampSoFar and LogSegment.offsetOfMaxTimestampSoFar are read/updated in sync

[ https://issues.apache.org/jira/browse/KAFKA-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-12981: --- Assignee: Tom Scott > Ensure LogSegment.maxTimestampSoFar and LogSegment.offsetOfMaxTimesta

[jira] [Commented] (KAFKA-13002) listOffsets must downgrade immediately for non MAX_TIMESTAMP specs

[ https://issues.apache.org/jira/browse/KAFKA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372740#comment-17372740 ] David Jacot commented on KAFKA-13002: - Awesome, thanks! > listOffsets must downgrad

[jira] [Commented] (KAFKA-13002) listOffsets must downgrade immediately for non MAX_TIMESTAMP specs

[ https://issues.apache.org/jira/browse/KAFKA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372621#comment-17372621 ] David Jacot commented on KAFKA-13002: - [~cadonna] Sounds good, thanks. > listOffset

[jira] [Commented] (KAFKA-13002) listOffsets must downgrade immediately for non MAX_TIMESTAMP specs

[ https://issues.apache.org/jira/browse/KAFKA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372426#comment-17372426 ] David Jacot commented on KAFKA-13002: - [~vvcephei] We have fixed the regression. Cou

[jira] [Updated] (KAFKA-13002) listOffsets must downgrade immediately for non MAX_TIMESTAMP specs

[ https://issues.apache.org/jira/browse/KAFKA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-13002: Summary: listOffsets must downgrade immediately for non MAX_TIMESTAMP specs (was: dev branch Stre

[jira] [Resolved] (KAFKA-13002) listOffsets must downgrade immediately for non MAX_TIMESTAMP specs

[ https://issues.apache.org/jira/browse/KAFKA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13002. - Reviewer: David Jacot Resolution: Fixed > listOffsets must downgrade immediately for non M

[jira] [Assigned] (KAFKA-13002) dev branch Streams not able to fetch end offsets from pre-3.0 brokers

[ https://issues.apache.org/jira/browse/KAFKA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13002: --- Assignee: Tom Scott (was: David Jacot) > dev branch Streams not able to fetch end offsets

[jira] [Assigned] (KAFKA-13002) dev branch Streams not able to fetch end offsets from pre-3.0 brokers

[ https://issues.apache.org/jira/browse/KAFKA-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot reassigned KAFKA-13002: --- Assignee: David Jacot > dev branch Streams not able to fetch end offsets from pre-3.0 broke

[jira] [Resolved] (KAFKA-12541) Extend ListOffset to fetch offset with max timestamp (KIP-734)

[ https://issues.apache.org/jira/browse/KAFKA-12541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-12541. - Reviewer: David Jacot Resolution: Fixed > Extend ListOffset to fetch offset with max times

[jira] [Updated] (KAFKA-12541) Extend ListOffset to fetch offset with max timestamp (KIP-734)

[ https://issues.apache.org/jira/browse/KAFKA-12541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12541: Summary: Extend ListOffset to fetch offset with max timestamp (KIP-734) (was: AdminClient.listOff

[jira] [Resolved] (KAFKA-12991) Fix unsafe access to `AbstractCoordinator.state`

[ https://issues.apache.org/jira/browse/KAFKA-12991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-12991. - Fix Version/s: 2.8.1 3.0.0 Reviewer: A. Sophie Blee-Goldman Re

[jira] [Created] (KAFKA-12991) Fix unsafe access to `AbstractCoordinator.state`

David Jacot created KAFKA-12991: --- Summary: Fix unsafe access to `AbstractCoordinator.state` Key: KAFKA-12991 URL: https://issues.apache.org/jira/browse/KAFKA-12991 Project: Kafka Issue Type: Bu

[jira] [Updated] (KAFKA-12989) `MockClient` should respect the request matcher passed to `prepareUnsupportedVersionResponse`

[ https://issues.apache.org/jira/browse/KAFKA-12989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12989: Description: The `MockClient` offers the possibility to prepare an unsupported version response w

[jira] [Created] (KAFKA-12989) `MockClient` should respect the request matcher passed to `prepareUnsupportedVersionResponse`

David Jacot created KAFKA-12989: --- Summary: `MockClient` should respect the request matcher passed to `prepareUnsupportedVersionResponse` Key: KAFKA-12989 URL: https://issues.apache.org/jira/browse/KAFKA-12989

[jira] [Updated] (KAFKA-12989) `MockClient` should respect the request matcher passed to `prepareUnsupportedVersionResponse`

[ https://issues.apache.org/jira/browse/KAFKA-12989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot updated KAFKA-12989: Issue Type: Bug (was: Improvement) > `MockClient` should respect the request matcher passed to >

[jira] [Resolved] (KAFKA-12898) Owned partitions in the subscription must be sorted

[ https://issues.apache.org/jira/browse/KAFKA-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-12898. - Fix Version/s: 2.8.1 Reviewer: A. Sophie Blee-Goldman Resolution: Fixed > Owned

<    2   3   4   5   6   7   8   9   >