[jira] [Commented] (KAFKA-19012) Messages ending up on the wrong topic

2025-08-07 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012663#comment-18012663 ] Jun Rao commented on KAFKA-19012: - [~dnadolny] : Thanks for your help. Please let us kno

[jira] [Commented] (KAFKA-19012) Messages ending up on the wrong topic

2025-07-29 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010720#comment-18010720 ] Jun Rao commented on KAFKA-19012: - [~dnadolny] :  This PR [https://github.com/apache/kaf

[jira] [Commented] (KAFKA-16174) Flaky test: testDescribeQuorumStatusSuccessful – org.apache.kafka.tools.MetadataQuorumCommandTest

2025-07-15 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007340#comment-18007340 ] Jun Rao commented on KAFKA-16174: - Also saw the following test failure in https://githu

[jira] [Commented] (KAFKA-19481) Fix flaky test AuthorizerIntegrationTest.testConsumerGroupHeartbeatWithRegex()

2025-07-15 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007339#comment-18007339 ] Jun Rao commented on KAFKA-19481: - Saw the following failure in https://github.com/apac

[jira] [Created] (KAFKA-19512) add missing MVs in MetadataVersionTest

2025-07-15 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19512: --- Summary: add missing MVs in MetadataVersionTest Key: KAFKA-19512 URL: https://issues.apache.org/jira/browse/KAFKA-19512 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-19451) Fix flaky test: RemoteIndexCacheTest.testCacheEntryIsDeletedOnRemoval()

2025-07-14 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19451. - Fix Version/s: 4.2.0 Resolution: Fixed Merged the PR to trunk. > Fix flaky test: RemoteIndexCach

[jira] [Resolved] (KAFKA-19452) Fix flaky test: LogRecoveryTest.testHWCheckpointWithFailuresMultipleLogSegments

2025-07-14 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19452. - Fix Version/s: 4.2.0 Resolution: Fixed merged the PR to trunk > Fix flaky test: > LogRecoveryTe

[jira] [Assigned] (KAFKA-19452) Fix flaky test: LogRecoveryTest.testHWCheckpointWithFailuresMultipleLogSegments

2025-07-14 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-19452: --- Assignee: Rajani Karuturi > Fix flaky test: > LogRecoveryTest.testHWCheckpointWithFailuresMultiple

[jira] [Resolved] (KAFKA-7442) forceUnmap mmap on linux when index resize

2025-07-08 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7442. Fix Version/s: 4.2.0 Resolution: Duplicate This is not fixed in https://issues.apache.org/jira/brows

[jira] [Resolved] (KAFKA-19390) AbstractIndex#resize() does not release old mmap on Linux

2025-07-08 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19390. - Fix Version/s: 4.2.0 Resolution: Fixed merged the PR to trunk > AbstractIndex#resize() does not

[jira] [Created] (KAFKA-19466) LogConcurrencyTest should close the log when the test completes

2025-07-02 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19466: --- Summary: LogConcurrencyTest should close the log when the test completes Key: KAFKA-19466 URL: https://issues.apache.org/jira/browse/KAFKA-19466 Project: Kafka Issue

[jira] [Commented] (KAFKA-19451) Fix flaky test: RemoteIndexCacheTest.testCacheEntryIsDeletedOnRemoval()

2025-06-30 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987066#comment-17987066 ] Jun Rao commented on KAFKA-19451: - [~isding_l] : Thanks for your interest. Feel free to

[jira] [Created] (KAFKA-19452) Fix flaky test: LogRecoveryTest.testHWCheckpointWithFailuresMultipleLogSegments

2025-06-30 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19452: --- Summary: Fix flaky test: LogRecoveryTest.testHWCheckpointWithFailuresMultipleLogSegments Key: KAFKA-19452 URL: https://issues.apache.org/jira/browse/KAFKA-19452 Project: Kafka

[jira] [Updated] (KAFKA-19451) Fix flaky test: RemoteIndexCacheTest.testCacheEntryIsDeletedOnRemoval()

2025-06-30 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19451: Description: Saw the following flaky test in [https://github.com/apache/kafka/actions/runs/15937660290/jo

[jira] [Commented] (KAFKA-19451) Fix flaky test: RemoteIndexCacheTest.testCacheEntryIsDeletedOnRemoval()

2025-06-30 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987010#comment-17987010 ] Jun Rao commented on KAFKA-19451: - The test call the following before checking if the de

[jira] [Updated] (KAFKA-19451) Fix flaky test: RemoteIndexCacheTest.testCacheEntryIsDeletedOnRemoval()

2025-06-30 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19451: Description: Saw the following flaky test in [https://github.com/apache/kafka/actions/runs/15937660290/jo

[jira] [Created] (KAFKA-19451) Fix flaky test: RemoteIndexCacheTest.testCacheEntryIsDeletedOnRemoval()

2025-06-30 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19451: --- Summary: Fix flaky test: RemoteIndexCacheTest.testCacheEntryIsDeletedOnRemoval() Key: KAFKA-19451 URL: https://issues.apache.org/jira/browse/KAFKA-19451 Project: Kafka

[jira] [Commented] (KAFKA-13077) Replication failing after unclean shutdown of ZK and all brokers

2025-06-24 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985958#comment-17985958 ] Jun Rao commented on KAFKA-13077: - [~gmcrobert] : Thanks for the reply. If the broker is

[jira] [Commented] (KAFKA-13077) Replication failing after unclean shutdown of ZK and all brokers

2025-06-23 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985722#comment-17985722 ] Jun Rao commented on KAFKA-13077: - [~gmcrobert] : Thanks for the analysis. So, it seems

[jira] [Updated] (KAFKA-19397) TransactionManager.handleCompletedBatch throws NPE

2025-06-10 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19397: Component/s: clients Affects Version/s: 4.1.0 Priority: Blocker (was: Major) > Tra

[jira] [Resolved] (KAFKA-19325) improve forceComplete() in DelayedOperation

2025-06-10 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19325. - Resolution: Won't Fix It seems that changing forceComplete() to return void makes the usage less conven

[jira] [Commented] (KAFKA-19012) Messages ending up on the wrong topic

2025-06-09 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957364#comment-17957364 ] Jun Rao commented on KAFKA-19012: - Thanks for the info, [~dnadolny]. > Messages ending

[jira] [Comment Edited] (KAFKA-19080) The constraint on segment.bytes is not enforced at topic level

2025-06-09 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940821#comment-17940821 ] Jun Rao edited comment on KAFKA-19080 at 6/9/25 8:35 PM: - [~iamo

[jira] [Updated] (KAFKA-19080) The constraint on segment.bytes is not enforced at topic level

2025-06-09 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19080: Summary: The constraint on segment.bytes is not enforced at topic level (was: The constraint on segment.m

[jira] [Commented] (KAFKA-19012) Messages ending up on the wrong topic

2025-06-05 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956484#comment-17956484 ] Jun Rao commented on KAFKA-19012: - [~dnadolny] : Thanks for the reporting this issue. Co

[jira] [Commented] (KAFKA-19325) improve forceComplete() in DelayedOperation

2025-05-23 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953779#comment-17953779 ] Jun Rao commented on KAFKA-19325: - [~m1a2st] : Thanks for your interest. I left the assi

[jira] [Resolved] (KAFKA-19326) flaky test GroupMetadataManagerTest.testShareGroupInitializeSuccess()

2025-05-23 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19326. - Fix Version/s: 4.1.0 Resolution: Fixed It seems this is fixed in [https://github.com/apache/kafka

[jira] [Created] (KAFKA-19326) flaky test GroupMetadataManagerTest.testShareGroupInitializeSuccess()

2025-05-23 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19326: --- Summary: flaky test GroupMetadataManagerTest.testShareGroupInitializeSuccess() Key: KAFKA-19326 URL: https://issues.apache.org/jira/browse/KAFKA-19326 Project: Kafka

[jira] [Updated] (KAFKA-19325) improve forceComplete() in DelayedOperation

2025-05-23 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19325: Description: After [https://github.com/apache/kafka/pull/19759/files,] DelayedOperation.forceComplete() a

[jira] [Created] (KAFKA-19325) improve forceComplete() in DelayedOperation

2025-05-23 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19325: --- Summary: improve forceComplete() in DelayedOperation Key: KAFKA-19325 URL: https://issues.apache.org/jira/browse/KAFKA-19325 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-19325) improve forceComplete() in DelayedOperation

2025-05-23 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19325: Description: After [https://github.com/apache/kafka/pull/19759/files,] DelayedOperation.forceComplete() a

[jira] [Resolved] (KAFKA-19234) broker should return UNAUTHORIZATION error for non-existing topic in produce request

2025-05-14 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19234. - Fix Version/s: 4.1.0 Resolution: Fixed merged the PR to trunk > broker should return UNAUTHORIZA

[jira] [Resolved] (KAFKA-19212) Fix ElectionWasClean bug when partition reassignment completes

2025-05-07 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19212. - Resolution: Fixed merged the PR to trunk > Fix ElectionWasClean bug when partition reassignment complet

[jira] [Commented] (KAFKA-19234) broker should return UNAUTHORIZATION error for non-existing topic in produce request

2025-05-03 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949165#comment-17949165 ] Jun Rao commented on KAFKA-19234: - [~yangpoan] : Thanks for your interest. Feel free to

[jira] [Commented] (KAFKA-19234) broker should return UNAUTHORIZATION error for non-existing topic in produce request

2025-05-02 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949112#comment-17949112 ] Jun Rao commented on KAFKA-19234: - It seems that the Fetch request does the right thing.

[jira] [Updated] (KAFKA-19234) broker should return UNAUTHORIZATION error for non-existing topic in produce request

2025-05-02 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19234: Description: In [https://github.com/apache/kafka/pull/15968/files], we changed the authorization logic sl

[jira] [Created] (KAFKA-19234) broker should return UNAUTHORIZATION error for non-existing topic in produce request

2025-05-02 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19234: --- Summary: broker should return UNAUTHORIZATION error for non-existing topic in produce request Key: KAFKA-19234 URL: https://issues.apache.org/jira/browse/KAFKA-19234 Project: K

[jira] [Resolved] (KAFKA-19019) Verify Share Fetch with Tiered Storage

2025-04-21 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19019. - Fix Version/s: 4.1.0 Resolution: Fixed merged the PR to trunk > Verify Share Fetch with Tiered S

[jira] [Updated] (KAFKA-19080) The constraint on segment.ms is not enforced at topic level

2025-04-15 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19080: Description: [https://cwiki.apache.org/confluence/display/KAFKA/KIP-1030%3A+Change+constraints+and+default

[jira] [Updated] (KAFKA-19080) The constraint on segment.ms is not enforced at topic level

2025-04-15 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-19080: Description: [https://cwiki.apache.org/confluence/display/KAFKA/KIP-1030%3A+Change+constraints+and+default

[jira] [Comment Edited] (KAFKA-19112) cleanup.policy shouldn't be empty

2025-04-14 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944402#comment-17944402 ] Jun Rao edited comment on KAFKA-19112 at 4/14/25 7:06 PM: -- [~ch

[jira] [Commented] (KAFKA-19112) cleanup.policy shouldn't be empty

2025-04-14 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944402#comment-17944402 ] Jun Rao commented on KAFKA-19112: - [~chia7712] : For infinite retention, we already supp

[jira] [Commented] (KAFKA-19112) cleanup.policy shouldn't be empty

2025-04-08 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942034#comment-17942034 ] Jun Rao commented on KAFKA-19112: - [~m1a2st] : Thanks for your interest. Feel free to ta

[jira] [Commented] (KAFKA-19112) cleanup.policy shouldn't be empty

2025-04-08 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942029#comment-17942029 ] Jun Rao commented on KAFKA-19112: - We can tighten up the validation for those configs. H

[jira] [Created] (KAFKA-19112) cleanup.policy shouldn't be empty

2025-04-08 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19112: --- Summary: cleanup.policy shouldn't be empty Key: KAFKA-19112 URL: https://issues.apache.org/jira/browse/KAFKA-19112 Project: Kafka Issue Type: Bug Components:

[jira] [Updated] (KAFKA-18991) AbstractFetcherThread should verify the current leader epoch in the fetch request matches the leader epoch in the fetch state

2025-04-08 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-18991: Fix Version/s: (was: 3.9.1) (was: 4.0.1) > AbstractFetcherThread should verify

[jira] [Resolved] (KAFKA-18991) AbstractFetcherThread should verify the current leader epoch in the fetch request matches the leader epoch in the fetch state

2025-04-08 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18991. - Resolution: Fixed > AbstractFetcherThread should verify the current leader epoch in the fetch > request

[jira] [Commented] (KAFKA-18991) AbstractFetcherThread should verify the current leader epoch in the fetch request matches the leader epoch in the fetch state

2025-04-08 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942020#comment-17942020 ] Jun Rao commented on KAFKA-18991: - merged the PR to trunk > AbstractFetcherThread shoul

[jira] [Commented] (KAFKA-15931) Cached transaction index gets closed if tiered storage read is interrupted

2025-04-05 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937171#comment-17937171 ] Jun Rao commented on KAFKA-15931: - Merged [https://github.com/apache/kafka/pull/19197] t

[jira] [Commented] (KAFKA-19080) The constraint on segment.ms is not enforced at topic level

2025-04-03 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940821#comment-17940821 ] Jun Rao commented on KAFKA-19080: - [~iamoshione] : I mean that if a request tries to cha

[jira] [Commented] (KAFKA-19080) The constraint on segment.ms is not enforced at topic level

2025-04-03 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940756#comment-17940756 ] Jun Rao commented on KAFKA-19080: - [~m1a2st] : Yes, feel free to take it. Thanks. > The

[jira] [Created] (KAFKA-19080) The constraint on segment.ms is not enforced at topic level

2025-04-02 Thread Jun Rao (Jira)
Jun Rao created KAFKA-19080: --- Summary: The constraint on segment.ms is not enforced at topic level Key: KAFKA-19080 URL: https://issues.apache.org/jira/browse/KAFKA-19080 Project: Kafka Issue Type

[jira] [Commented] (KAFKA-15931) Cached transaction index gets closed if tiered storage read is interrupted

2025-04-01 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940188#comment-17940188 ] Jun Rao commented on KAFKA-15931: - Cherry-picked the PR to 3.9 and 4.0 too. > Cached tr

[jira] [Updated] (KAFKA-15931) Cached transaction index gets closed if tiered storage read is interrupted

2025-04-01 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-15931: Fix Version/s: 3.9.1 4.0.1 > Cached transaction index gets closed if tiered storage rea

[jira] [Created] (KAFKA-18991) AbstractFetcherThread should verify the current leader epoch in the fetch request matches the leader epoch in the fetch state

2025-03-15 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18991: --- Summary: AbstractFetcherThread should verify the current leader epoch in the fetch request matches the leader epoch in the fetch state Key: KAFKA-18991 URL: https://issues.apache.org/jira/b

[jira] [Resolved] (KAFKA-18606) Flaky test DeleteSegmentsByRetentionTimeTest#executeTieredStorageTest

2025-03-14 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18606. - Resolution: Fixed merged the PR to trunk. > Flaky test DeleteSegmentsByRetentionTimeTest#executeTieredS

[jira] [Commented] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-03-05 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932712#comment-17932712 ] Jun Rao commented on KAFKA-18477: - [~chia7712] : Good point. If the follower doesn't hav

[jira] [Commented] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-03-04 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932421#comment-17932421 ] Jun Rao commented on KAFKA-18477: - So, to summarize, we can remove the usage of OffsetFo

[jira] [Commented] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-03-04 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932418#comment-17932418 ] Jun Rao commented on KAFKA-18477: - {quote}do you mean the truncation logic using the hig

[jira] [Commented] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-03-03 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932050#comment-17932050 ] Jun Rao commented on KAFKA-18477: - [~chia7712] : To send an OffsetForLeaderRequest, we n

[jira] [Resolved] (KAFKA-18844) Stale features information in QuorumController#registerBroker

2025-03-03 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18844. - Resolution: Fixed The PR is merged to trunk, 4.0 and 3.9. > Stale features information in QuorumControl

[jira] [Commented] (KAFKA-18876) 4.0 documentation improvement

2025-03-01 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931576#comment-17931576 ] Jun Rao commented on KAFKA-18876: - [~mingdaoy] : Thanks for picking up this jira. Since

[jira] [Resolved] (KAFKA-18864) remove the Evolving tag from stable public interfaces

2025-02-28 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18864. - Fix Version/s: 4.1.0 Resolution: Fixed > remove the Evolving tag from stable public interfaces >

[jira] [Commented] (KAFKA-18876) 4.0 documentation improvement

2025-02-26 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17930873#comment-17930873 ] Jun Rao commented on KAFKA-18876: - A few other improvements. 1. bin/kafka-storage.sh fo

[jira] [Created] (KAFKA-18876) 4.0 documentation improvement

2025-02-26 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18876: --- Summary: 4.0 documentation improvement Key: KAFKA-18876 URL: https://issues.apache.org/jira/browse/KAFKA-18876 Project: Kafka Issue Type: Improvement Affects Versi

[jira] [Created] (KAFKA-18864) remove the Evolving tag from public interfaces in org.apache.kafka.server.log.remote.storage

2025-02-25 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18864: --- Summary: remove the Evolving tag from public interfaces in org.apache.kafka.server.log.remote.storage Key: KAFKA-18864 URL: https://issues.apache.org/jira/browse/KAFKA-18864 Pr

[jira] [Commented] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-02-20 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928899#comment-17928899 ] Jun Rao commented on KAFKA-18477: - [~m1a2st] : Sorry for the late reply. We can change

[jira] [Commented] (KAFKA-18723) KRaft must handle corrupted records in the fetch response

2025-02-12 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926585#comment-17926585 ] Jun Rao commented on KAFKA-18723: - [~jsancio] : Good point. I think we can tighten this

[jira] [Commented] (KAFKA-18762) 'Acks=all' not working correctly in Kafka Kraft mode.

2025-02-10 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925654#comment-17925654 ] Jun Rao commented on KAFKA-18762: - It's possible to change the replication factor throug

[jira] [Commented] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-02-06 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924745#comment-17924745 ] Jun Rao commented on KAFKA-18477: - [~m1a2st] : In AbstractFetcherThread, we have the fo

[jira] [Comment Edited] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-02-06 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924745#comment-17924745 ] Jun Rao edited comment on KAFKA-18477 at 2/7/25 1:07 AM: - [~m1a2

[jira] [Commented] (KAFKA-18723) KRaft must handle corrupted records in the fetch response

2025-02-06 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924642#comment-17924642 ] Jun Rao commented on KAFKA-18723: -   {noformat} For this solution to work for ISR partit

[jira] [Commented] (KAFKA-18723) KRaft must handle corrupted records in the fetch response

2025-02-05 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924303#comment-17924303 ] Jun Rao commented on KAFKA-18723: - [~jsancio] : Thanks for reporting this. This does see

[jira] [Resolved] (KAFKA-18683) File records slice errors when sliced for moved start position

2025-01-31 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18683. - Fix Version/s: 4.1.0 Resolution: Fixed merged the PR to trunk. > File records slice errors when

[jira] [Commented] (KAFKA-18522) Limit fetch records batches as per acquired records

2025-01-30 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922512#comment-17922512 ] Jun Rao commented on KAFKA-18522: - [~apoorvmittal10] : Thanks for finding this. I think

[jira] [Resolved] (KAFKA-18668) config/kraft/reconfig-server.properties no longer exists in quickstart

2025-01-29 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18668. - Resolution: Implemented [~mimaison] : Thanks for the info. That PR covers this need. Closing this jira.

[jira] [Created] (KAFKA-18668) config/kraft/reconfig-server.properties no longer exists in quickstart

2025-01-29 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18668: --- Summary: config/kraft/reconfig-server.properties no longer exists in quickstart Key: KAFKA-18668 URL: https://issues.apache.org/jira/browse/KAFKA-18668 Project: Kafka

[jira] [Commented] (KAFKA-15640) Refactor CompletedFetch initialization

2025-01-27 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-15640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921564#comment-17921564 ] Jun Rao commented on KAFKA-15640: - The first issue. This doesn't seem to be a real issue

[jira] [Commented] (KAFKA-18641) AsyncKafkaConsumer could lose records with auto offset commit

2025-01-24 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916877#comment-17916877 ] Jun Rao commented on KAFKA-18641: - [~frankvicky] : Thanks for your interest. Feel free t

[jira] [Commented] (KAFKA-18522) Limit fetch records batches as per acquired records

2025-01-24 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916806#comment-17916806 ] Jun Rao commented on KAFKA-18522: - [~apoorvmittal10] : Yes, FileRecords just points to a

[jira] [Resolved] (KAFKA-17894) Additional metrics for cooperative consumption

2025-01-24 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-17894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-17894. - Fix Version/s: 4.1.0 Resolution: Fixed Merged the PR to trunk. > Additional metrics for cooperat

[jira] [Created] (KAFKA-18641) AsyncKafkaConsumer could lose records with auto offset commit

2025-01-24 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18641: --- Summary: AsyncKafkaConsumer could lose records with auto offset commit Key: KAFKA-18641 URL: https://issues.apache.org/jira/browse/KAFKA-18641 Project: Kafka Issue Ty

[jira] [Resolved] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

2025-01-23 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18625. - Resolution: Not A Problem > consumer client could get duplicated records if assigned partitions change

[jira] [Commented] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

2025-01-23 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916518#comment-17916518 ] Jun Rao commented on KAFKA-18625: - On further look, it seems this is not a problem.  In

[jira] [Commented] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

2025-01-22 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916232#comment-17916232 ] Jun Rao commented on KAFKA-18625: - [~frankvicky] : Thanks for your interest. Feel free t

[jira] [Commented] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

2025-01-22 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916216#comment-17916216 ] Jun Rao commented on KAFKA-18625: - [~chia7712] : Thanks. Yes, updated the description.

[jira] [Updated] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

2025-01-22 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-18625: Description: When a partition is unassigned to a consumer, we don't clear the buffered records in the cli

[jira] [Commented] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

2025-01-22 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916172#comment-17916172 ] Jun Rao commented on KAFKA-18625: - [~hachikuji] : Do you think this is a real issue? Tha

[jira] [Created] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

2025-01-22 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18625: --- Summary: consumer client could get duplicated records if assigned partitions change quickly Key: KAFKA-18625 URL: https://issues.apache.org/jira/browse/KAFKA-18625 Project: Kaf

[jira] [Resolved] (KAFKA-806) Index may not always observe log.index.interval.bytes

2025-01-17 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-806. --- Fix Version/s: 4.1.0 Resolution: Fixed merged [https://github.com/apache/kafka/pull/18012] to trunk >

[jira] [Resolved] (KAFKA-18452) Integrate share fetch batch size in share fetch

2025-01-15 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18452. - Fix Version/s: 4.1.0 Resolution: Fixed merged the PR to trunk > Integrate share fetch batch size

[jira] [Created] (KAFKA-18479) remove keepPartitionMetadataFile in UnifiedLog and LogManager

2025-01-11 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18479: --- Summary: remove keepPartitionMetadataFile in UnifiedLog and LogManager Key: KAFKA-18479 URL: https://issues.apache.org/jira/browse/KAFKA-18479 Project: Kafka Issue Ty

[jira] [Commented] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-01-10 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912160#comment-17912160 ] Jun Rao commented on KAFKA-18477: - [~m1a2st] : Thanks for helping out. Feel free to take

[jira] [Created] (KAFKA-18477) remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread

2025-01-10 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18477: --- Summary: remove usage of OffsetForLeaderEpochRequest in AbstractFetcherThread Key: KAFKA-18477 URL: https://issues.apache.org/jira/browse/KAFKA-18477 Project: Kafka I

[jira] [Commented] (KAFKA-18177) generate better helper code to support changing keys in request/response schema

2024-12-06 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903783#comment-17903783 ] Jun Rao commented on KAFKA-18177: - [~frankvicky] : Thanks for helping out. Feel free to

[jira] [Created] (KAFKA-18177) generate better helper code to support changing keys in request/response schema

2024-12-06 Thread Jun Rao (Jira)
Jun Rao created KAFKA-18177: --- Summary: generate better helper code to support changing keys in request/response schema Key: KAFKA-18177 URL: https://issues.apache.org/jira/browse/KAFKA-18177 Project: Kafka

[jira] [Resolved] (KAFKA-18052) Decouple the dependency of feature stable version to the metadata version

2024-12-05 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18052. - Fix Version/s: 4.0.0 Resolution: Fixed merged the PR to trunk > Decouple the dependency of featu

[jira] [Resolved] (KAFKA-17783) Remove sharePartition from SharePartitionManager if the partition is deleted or becomes a follower

2024-12-04 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-17783. - Fix Version/s: 4.0.0 Resolution: Fixed merged the PR to trunk > Remove sharePartition from Share

[jira] [Resolved] (KAFKA-18027) MINOR: Correct DelayedOperationPurgatory code around adding of an already completed operation

2024-11-20 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18027. - Fix Version/s: 4.0.0 Resolution: Fixed merged the PR to trunk. > MINOR: Correct DelayedOperation

[jira] [Resolved] (KAFKA-18022) fetchOffsetMetadata handling for minBytes estimation in both common/uncommon cases of share fetch

2024-11-16 Thread Jun Rao (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18022. - Fix Version/s: 4.0.0 Resolution: Fixed merged the PR to trunk. > fetchOffsetMetadata handling fo

  1   2   3   4   5   6   7   >