[jira] [Resolved] (KAFKA-13407) Kafka controller out of service after ZK leader restart

[ https://issues.apache.org/jira/browse/KAFKA-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13407. - Resolution: Fixed > Kafka controller out of service after ZK leader restart >

[jira] [Commented] (KAFKA-13407) Kafka controller out of service after ZK leader restart

[ https://issues.apache.org/jira/browse/KAFKA-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17497760#comment-17497760 ] Jun Rao commented on KAFKA-13407: - [~Olsson] : Thanks for the reply. I think we fixed this issue in

[jira] [Resolved] (KAFKA-13603) empty active segment can trigger recovery after clean shutdown and restart

[ https://issues.apache.org/jira/browse/KAFKA-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13603. - Fix Version/s: 3.2.0 Resolution: Fixed merged the PR to trunk. > empty active segment can

[jira] [Commented] (KAFKA-13594) In TNPM Wireline Project, vulnerability found in Log4j-1.2.17.jar under KAFKA directory

[ https://issues.apache.org/jira/browse/KAFKA-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476483#comment-17476483 ] Jun Rao commented on KAFKA-13594: - [~Waseem_bhura] : Once you remove JMSAppender, it shouldn't affect

[jira] [Commented] (KAFKA-13594) In TNPM Wireline Project, vulnerability found in Log4j-1.2.17.jar under KAFKA directory

[ https://issues.apache.org/jira/browse/KAFKA-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17475831#comment-17475831 ] Jun Rao commented on KAFKA-13594: - [~Waseem_bhura] : You can refer to

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472207#comment-17472207 ] Jun Rao commented on KAFKA-2729: [~mgabriel] : The BadVersion on ZK server just indicates that a

[jira] [Commented] (KAFKA-13574) NotLeaderOrFollowerException thrown for a successful send

[ https://issues.apache.org/jira/browse/KAFKA-13574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468275#comment-17468275 ] Jun Rao commented on KAFKA-13574: - [~aphyr] : Thanks for reporting this issue. [~hachikuji] : Thanks for

[jira] [Updated] (KAFKA-13544) Deadlock during shutting down kafka broker because of connectivity problem with zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-13544: Fix Version/s: (was: 3.2.0) > Deadlock during shutting down kafka broker because of connectivity

[jira] [Updated] (KAFKA-13544) Deadlock during shutting down kafka broker because of connectivity problem with zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-13544: Fix Version/s: 3.1.0 3.0.1 2.8.2 [~andrei-vlg] : I merged the PR to

[jira] [Resolved] (KAFKA-13544) Deadlock during shutting down kafka broker because of connectivity problem with zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13544. - Fix Version/s: 3.2.0 Resolution: Fixed Merged the PR to trunk. > Deadlock during shutting down

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

[ https://issues.apache.org/jira/browse/KAFKA-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461720#comment-17461720 ] Jun Rao commented on KAFKA-13077: - [~shivakumar] : So, it seems the issue is unrelated to file

[jira] [Resolved] (KAFKA-13551) kafka-log4j-appender-2.1.1.jar Is cve-2021-44228 involved?

[ https://issues.apache.org/jira/browse/KAFKA-13551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13551. - Resolution: Information Provided The impact is described in [https://kafka.apache.org/cve-list] >

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

[ https://issues.apache.org/jira/browse/KAFKA-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17459555#comment-17459555 ] Jun Rao commented on KAFKA-13077: - [~shivakumar] : The mismatches in 14022515.index are

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

[ https://issues.apache.org/jira/browse/KAFKA-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456057#comment-17456057 ] Jun Rao commented on KAFKA-13077: - [~shivakumar] : Not sure what's leading to the warning. It would be

[jira] [Resolved] (KAFKA-13202) KIP-768: Extend SASL/OAUTHBEARER with Support for OIDC

[ https://issues.apache.org/jira/browse/KAFKA-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13202. - Fix Version/s: 3.1.0 Resolution: Fixed merged the PR to trunk. > KIP-768: Extend

[jira] [Resolved] (KAFKA-12802) Add a file based cache for consumed remote log metadata for each partition to avoid consuming again incase of broker restarts.

[ https://issues.apache.org/jira/browse/KAFKA-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12802. - Resolution: Fixed merged the PR to trunk > Add a file based cache for consumed remote log metadata for

[jira] [Resolved] (KAFKA-13305) NullPointerException in LogCleanerManager "uncleanable-bytes" gauge

[ https://issues.apache.org/jira/browse/KAFKA-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13305. - Fix Version/s: 3.1.0 Assignee: Vincent Jiang Resolution: Fixed merged the PR trunk. >

[jira] [Resolved] (KAFKA-13070) LogManager shutdown races with periodic work scheduled by the instance

[ https://issues.apache.org/jira/browse/KAFKA-13070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13070. - Resolution: Duplicate > LogManager shutdown races with periodic work scheduled by the instance >

[jira] [Resolved] (KAFKA-13315) log layer exception during shutdown that caused an unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13315. - Fix Version/s: 3.0.1 3.1.0 Resolution: Fixed merged the PR to trunk and 3.0.

[jira] [Created] (KAFKA-13313) In KRaft mode, CreateTopic should return the topic configs in the response

Jun Rao created KAFKA-13313: --- Summary: In KRaft mode, CreateTopic should return the topic configs in the response Key: KAFKA-13313 URL: https://issues.apache.org/jira/browse/KAFKA-13313 Project: Kafka

[jira] [Commented] (KAFKA-8522) Tombstones can survive forever

[ https://issues.apache.org/jira/browse/KAFKA-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416231#comment-17416231 ] Jun Rao commented on KAFKA-8522: The implementation design can be found at KIP-534: 

[jira] [Resolved] (KAFKA-8522) Tombstones can survive forever

[ https://issues.apache.org/jira/browse/KAFKA-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-8522. Fix Version/s: 3.1.0 Assignee: Richard Yu Resolution: Fixed Finally, merged the PR to

[jira] [Commented] (KAFKA-8334) Occasional OffsetCommit Timeout

[ https://issues.apache.org/jira/browse/KAFKA-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17412714#comment-17412714 ] Jun Rao commented on KAFKA-8334: [~geek-chen]: This is a server side issue. So you will need to upgrade

[jira] [Resolved] (KAFKA-12988) Change RLMM add/updateRemoteLogSegmentMetadata and putRemotePartitionDeleteMetadata APIS asynchronous.

[ https://issues.apache.org/jira/browse/KAFKA-12988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12988. - Fix Version/s: 3.1.0 Resolution: Fixed merged the PR to trunk. > Change RLMM

[jira] [Resolved] (KAFKA-13225) Controller skips sending UpdateMetadataRequest when shutting down broker doesnt host partitions

[ https://issues.apache.org/jira/browse/KAFKA-13225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13225. - Fix Version/s: 3.1.0 Resolution: Fixed merged the PR to trunk > Controller skips sending

[jira] [Resolved] (KAFKA-13198) TopicsDelta doesn't update deleted topic when processing PartitionChangeRecord

[ https://issues.apache.org/jira/browse/KAFKA-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13198. - Resolution: Fixed merged the PR to 3.0 and trunk. > TopicsDelta doesn't update deleted topic when

[jira] [Commented] (KAFKA-13206) shutting down broker needs to stop fetching as a follower in KRaft mode

[ https://issues.apache.org/jira/browse/KAFKA-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399978#comment-17399978 ] Jun Rao commented on KAFKA-13206: - It's probably after the controller has acted on the controlled

[jira] [Commented] (KAFKA-13206) shutting down broker needs to stop fetching as a follower in KRaft mode

[ https://issues.apache.org/jira/browse/KAFKA-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399908#comment-17399908 ] Jun Rao commented on KAFKA-13206: - [~cmccabe] mentioned the following. The broker being shut down in

[jira] [Created] (KAFKA-13206) shutting down broker needs to stop fetching as a follower in KRaft mode

Jun Rao created KAFKA-13206: --- Summary: shutting down broker needs to stop fetching as a follower in KRaft mode Key: KAFKA-13206 URL: https://issues.apache.org/jira/browse/KAFKA-13206 Project: Kafka

[jira] [Resolved] (KAFKA-13194) LogCleaner may clean past highwatermark

[ https://issues.apache.org/jira/browse/KAFKA-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13194. - Fix Version/s: 3.1.0 Assignee: Lucas Bradstreet Resolution: Fixed Merged the PR to

[jira] [Resolved] (KAFKA-13068) Rename Log to UnifiedLog

[ https://issues.apache.org/jira/browse/KAFKA-13068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13068. - Fix Version/s: 3.1.0 Resolution: Fixed Merged the PR to trunk > Rename Log to UnifiedLog >

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17396210#comment-17396210 ] Jun Rao commented on KAFKA-2729: [~axrj]: If broker 5's ZK session expires and gets re-established, its

[jira] [Commented] (KAFKA-12418) Make sure it's ok not to include test jars in the release tarball

[ https://issues.apache.org/jira/browse/KAFKA-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17384345#comment-17384345 ] Jun Rao commented on KAFKA-12418: - That seems fine since most people who depend on the test jar use the

[jira] [Resolved] (KAFKA-9555) Topic-based implementation for the RemoteLogMetadataManager

[ https://issues.apache.org/jira/browse/KAFKA-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-9555. Resolution: Fixed merged the PR to trunk. > Topic-based implementation for the RemoteLogMetadataManager >

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

[ https://issues.apache.org/jira/browse/KAFKA-13092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13092. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to 3.0 and trunk. > Perf regression in

[jira] [Resolved] (KAFKA-12554) Split Log layer into Log and LocalLog

[ https://issues.apache.org/jira/browse/KAFKA-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12554. - Fix Version/s: 3.1.0 Resolution: Fixed merged the PR to trunk. > Split Log layer into Log and

[jira] [Resolved] (KAFKA-10580) Add topic ID support to Fetch request

[ https://issues.apache.org/jira/browse/KAFKA-10580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10580. - Fix Version/s: 3.1.0 Resolution: Fixed merged the PR to trunk. > Add topic ID support to Fetch

[jira] [Resolved] (KAFKA-12964) Corrupt segment recovery can delete new producer state snapshots

[ https://issues.apache.org/jira/browse/KAFKA-12964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12964. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Corrupt segment recovery can

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372214#comment-17372214 ] Jun Rao commented on KAFKA-2729: [~l0co] the leaderEpoch doesn't always match the zkVersion. For example,

[jira] [Resolved] (KAFKA-12520) Producer state is needlessly rebuilt on startup

[ https://issues.apache.org/jira/browse/KAFKA-12520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12520. - Fix Version/s: 3.0.0 Assignee: Cong Ding (was: Dhruvil Shah) Resolution: Fixed merged

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370724#comment-17370724 ] Jun Rao commented on KAFKA-2729: [~l0co], thanks for reporting this. The "Cached zkVersion [212]" error

[jira] [Resolved] (KAFKA-12816) Add tier storage configs.

[ https://issues.apache.org/jira/browse/KAFKA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12816. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Add tier storage configs. >

[jira] [Resolved] (KAFKA-12955) Fix LogLoader to pass materialized view of segments for deletion

[ https://issues.apache.org/jira/browse/KAFKA-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12955. - Fix Version/s: 3.0.0 Assignee: Kowshik Prakasam Resolution: Fixed Merged the PR to

[jira] [Created] (KAFKA-12852) Log.splitOverflowedSegment() doesn't generate producer snapshot for new segment

Jun Rao created KAFKA-12852: --- Summary: Log.splitOverflowedSegment() doesn't generate producer snapshot for new segment Key: KAFKA-12852 URL: https://issues.apache.org/jira/browse/KAFKA-12852 Project: Kafka

[jira] [Commented] (KAFKA-8522) Tombstones can survive forever

[ https://issues.apache.org/jira/browse/KAFKA-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350551#comment-17350551 ] Jun Rao commented on KAFKA-8522: latest PR link > Tombstones can survive forever >

[jira] [Commented] (KAFKA-3968) fsync() is not called on parent directory when new FileMessageSet is flushed to disk

[ https://issues.apache.org/jira/browse/KAFKA-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17344701#comment-17344701 ] Jun Rao commented on KAFKA-3968: Merged the reworked PR [https://github.com/apache/kafka/pull/10680] to

[jira] [Commented] (KAFKA-9826) Log cleaning repeatedly picks same segment with no effect when first dirty offset is past start of active segment

[ https://issues.apache.org/jira/browse/KAFKA-9826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342904#comment-17342904 ] Jun Rao commented on KAFKA-9826: [~zhangzs] : The issue was fixed in 2.4.2. Could you try that version?

[jira] [Resolved] (KAFKA-12758) Create a new `server-common` module and move ApiMessageAndVersion, RecordSerde, AbstractApiMessageSerde, and BytesApiMessageSerde to that module.

[ https://issues.apache.org/jira/browse/KAFKA-12758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12758. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Create a new `server-common`

[jira] [Commented] (KAFKA-12757) Move server related common and public classes into separate module(s).

[ https://issues.apache.org/jira/browse/KAFKA-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342023#comment-17342023 ] Jun Rao commented on KAFKA-12757: - [~satish.duggana]: The implementation of server side APIs may depend

[jira] [Resolved] (KAFKA-12429) Serdes for all message types in internal topic which is used in default implementation for RLMM.

[ https://issues.apache.org/jira/browse/KAFKA-12429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12429. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Serdes for all message types in

[jira] [Resolved] (KAFKA-12553) Refactor Log layer recovery logic

[ https://issues.apache.org/jira/browse/KAFKA-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12553. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Refactor Log layer recovery

[jira] [Resolved] (KAFKA-12368) Inmemory implementation of RSM and RLMM.

[ https://issues.apache.org/jira/browse/KAFKA-12368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12368. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Inmemory implementation of RSM

[jira] [Resolved] (KAFKA-3968) fsync() is not called on parent directory when new FileMessageSet is flushed to disk

[ https://issues.apache.org/jira/browse/KAFKA-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3968. Fix Version/s: 3.0.0 Assignee: Cong Ding Resolution: Fixed Merged to trunk. Thanks Cong

[jira] [Resolved] (KAFKA-12575) Eliminate Log.isLogDirOffline boolean attribute

[ https://issues.apache.org/jira/browse/KAFKA-12575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12575. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Eliminate Log.isLogDirOffline

[jira] [Resolved] (KAFKA-12571) Eliminate LeaderEpochFileCache constructor dependency on LogEndOffset

[ https://issues.apache.org/jira/browse/KAFKA-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12571. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Eliminate LeaderEpochFileCache

[jira] [Resolved] (KAFKA-12552) Extract segments map out of Log class into separate class

[ https://issues.apache.org/jira/browse/KAFKA-12552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12552. - Fix Version/s: 3.0.0 Resolution: Fixed Merged the PR to trunk. > Extract segments map out of

[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=17297596#comment-17297596 ] Jun Rao commented on KAFKA-12431: - Hmm, I am not aware of any changes for throttling that could cause

[jira] [Resolved] (KAFKA-9548) SPI - RemoteStorageManager and RemoteLogMetadataManager interfaces and related classes.

[ https://issues.apache.org/jira/browse/KAFKA-9548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-9548. Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > SPI - RemoteStorageManager and

[jira] [Resolved] (KAFKA-12177) Retention is not idempotent

[ https://issues.apache.org/jira/browse/KAFKA-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-12177. - Fix Version/s: 3.0.0 Assignee: Lucas Bradstreet Resolution: Fixed merged the PR to

[jira] [Resolved] (KAFKA-9672) Dead brokers in ISR cause isr-expiration to fail with exception

[ https://issues.apache.org/jira/browse/KAFKA-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-9672. Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk > Dead brokers in ISR cause

[jira] [Commented] (KAFKA-10888) Sticky partition leads to uneven product msg, resulting in abnormal delays in some partations

[ https://issues.apache.org/jira/browse/KAFKA-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286039#comment-17286039 ] Jun Rao commented on KAFKA-10888: - [~hachikuji]: Thanks for the analysis. One thing that led to this

[jira] [Commented] (KAFKA-12176) Consider changing default log.message.timestamp.difference.max.ms

[ https://issues.apache.org/jira/browse/KAFKA-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263020#comment-17263020 ] Jun Rao commented on KAFKA-12176: - Another complication in the previous discussion was whether this

[jira] [Commented] (KAFKA-10759) ARM support for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17262814#comment-17262814 ] Jun Rao commented on KAFKA-10759: - [~xiaopenglei] : Thanks for your help. Perhaps you could first follow

[jira] [Created] (KAFKA-12153) follower can hit OffsetOutOfRangeException during truncation

Jun Rao created KAFKA-12153: --- Summary: follower can hit OffsetOutOfRangeException during truncation Key: KAFKA-12153 URL: https://issues.apache.org/jira/browse/KAFKA-12153 Project: Kafka Issue

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259314#comment-17259314 ] Jun Rao commented on KAFKA-2729: If you still see this issue, it would be useful to confirm the

[jira] [Commented] (KAFKA-10888) Sticky partition leads to uneven product msg, resulting in abnormal delays in some partations

[ https://issues.apache.org/jira/browse/KAFKA-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17254596#comment-17254596 ] Jun Rao commented on KAFKA-10888: - [~jr981008]: Thanks for reporting this. There are a couple of threads

[jira] [Commented] (KAFKA-10853) Replication protocol deficiencies with workloads requiring high durability guarantees

[ https://issues.apache.org/jira/browse/KAFKA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250568#comment-17250568 ] Jun Rao commented on KAFKA-10853: - [~ambroff] : Thanks for reporting this. I agree that this is real

[jira] [Commented] (KAFKA-10759) ARM support for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250438#comment-17250438 ] Jun Rao commented on KAFKA-10759: - [~xiaopenglei]: Thanks for the jira. Perhaps we can file an Apache

[jira] [Commented] (KAFKA-9087) ReplicaAlterLogDirs stuck and restart fails with java.lang.IllegalStateException: Offset mismatch for the future replica

[ https://issues.apache.org/jira/browse/KAFKA-9087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249973#comment-17249973 ] Jun Rao commented on KAFKA-9087: Not sure if this is exactly the reason, but we did fix an issue

[jira] [Updated] (KAFKA-9393) DeleteRecords may cause extreme lock contention for large partition directories

[ https://issues.apache.org/jira/browse/KAFKA-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-9393: --- Fix Version/s: (was: 2.7.0) 2.8.0 > DeleteRecords may cause extreme lock contention

[jira] [Commented] (KAFKA-10760) In compacted topic with max.compaction.lag.ms, the segments are not rolled until new messages arrive

[ https://issues.apache.org/jira/browse/KAFKA-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249409#comment-17249409 ] Jun Rao commented on KAFKA-10760: - [~kbrajesh176]: For max.compaction.lag.ms, we simply set segment.ms

[jira] [Resolved] (KAFKA-10832) Recovery logic is using incorrect ProducerStateManager instance when updating producers

[ https://issues.apache.org/jira/browse/KAFKA-10832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10832. - Fix Version/s: 2.8.0 Resolution: Fixed Merged the PR to trunk. > Recovery logic is using

[jira] [Resolved] (KAFKA-10723) LogManager leaks internal thread pool activity during shutdown

[ https://issues.apache.org/jira/browse/KAFKA-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10723. - Fix Version/s: 2.8.0 Resolution: Fixed merged to trunk > LogManager leaks internal thread pool

[jira] [Commented] (KAFKA-10734) Speedup the processing of LeaderAndIsr request

[ https://issues.apache.org/jira/browse/KAFKA-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234891#comment-17234891 ] Jun Rao commented on KAFKA-10734: - [~luwang], thanks for the jira. In practice, if n is large, m could

[jira] [Resolved] (KAFKA-10624) [Easy] FeatureZNodeStatus should use sealed trait instead of Enumeration

[ https://issues.apache.org/jira/browse/KAFKA-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10624. - Fix Version/s: 2.8.0 Resolution: Fixed merged the PR to trunk. > [Easy] FeatureZNodeStatus

[jira] [Commented] (KAFKA-9892) Producer state snapshot needs to be forced to disk

[ https://issues.apache.org/jira/browse/KAFKA-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223094#comment-17223094 ] Jun Rao commented on KAFKA-9892: [~kbrajesh176]: Thanks for your interest. Just added you to Kafka

[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=17221624#comment-17221624 ] Jun Rao commented on KAFKA-7987: [~rsivaram], yes, I think this issue still exists on all versions of

[jira] [Resolved] (KAFKA-10599) Implement basic CLI tool for feature versioning system

[ https://issues.apache.org/jira/browse/KAFKA-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10599. - Fix Version/s: 2.7.0 Resolution: Fixed Merged the PR to 2.7 and trunk. > Implement basic CLI

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17216963#comment-17216963 ] Jun Rao commented on KAFKA-3042: [~manme...@gmail.com]: Thanks for the update. It would be useful to get

[jira] [Resolved] (KAFKA-9393) DeleteRecords may cause extreme lock contention for large partition directories

[ https://issues.apache.org/jira/browse/KAFKA-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-9393. Fix Version/s: 2.7.0 Assignee: Gardner Vickers Resolution: Fixed merged to trunk. >

[jira] [Created] (KAFKA-10584) IndexSearchType should use sealed trait instead of Enumeration

Jun Rao created KAFKA-10584: --- Summary: IndexSearchType should use sealed trait instead of Enumeration Key: KAFKA-10584 URL: https://issues.apache.org/jira/browse/KAFKA-10584 Project: Kafka Issue

[jira] [Resolved] (KAFKA-10028) Implement write path for feature versioning scheme

[ https://issues.apache.org/jira/browse/KAFKA-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10028. - Fix Version/s: 2.7.0 Resolution: Fixed merged the PR to trunk > Implement write path for

[jira] [Deleted] (KAFKA-7590) GETTING HUGE MESSAGE STRUCTURE THROUGH JMS CONNECTOR

[ https://issues.apache.org/jira/browse/KAFKA-7590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao deleted KAFKA-7590: --- > GETTING HUGE MESSAGE STRUCTURE THROUGH JMS CONNECTOR > >

[jira] [Assigned] (KAFKA-8334) Occasional OffsetCommit Timeout

[ https://issues.apache.org/jira/browse/KAFKA-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao reassigned KAFKA-8334: -- Fix Version/s: 2.7.0 Assignee: Chia-Ping Tsai Resolution: Fixed Merged the PR to

[jira] [Commented] (KAFKA-10471) TimeIndex handling may cause data loss in certain back to back failure

[ https://issues.apache.org/jira/browse/KAFKA-10471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192503#comment-17192503 ] Jun Rao commented on KAFKA-10471: - [~dhruvilshah] : I agree that the sanity check in the index file is

[jira] [Commented] (KAFKA-10471) TimeIndex handling may cause data loss in certain back to back failure

[ https://issues.apache.org/jira/browse/KAFKA-10471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192492#comment-17192492 ] Jun Rao commented on KAFKA-10471: - [~rshekhar]: Thanks for reporting this. This is a very good finding.

[jira] [Commented] (KAFKA-8764) LogCleanerManager endless loop while compacting/cleaning segments

[ https://issues.apache.org/jira/browse/KAFKA-8764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17189684#comment-17189684 ] Jun Rao commented on KAFKA-8764: [~wushujames]: Yes, reassigned replica can have the same issue. >

[jira] [Resolved] (KAFKA-10300) fix flaky core/group_mode_transactions_test.py

[ https://issues.apache.org/jira/browse/KAFKA-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10300. - Fix Version/s: 2.7.0 Resolution: Fixed merged to trunk > fix flaky

[jira] [Resolved] (KAFKA-10274) Transaction system test uses inconsistent timeouts

[ https://issues.apache.org/jira/browse/KAFKA-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10274. - Fix Version/s: 2.6.0 Resolution: Fixed Merged this to trunk and 2.6 branch. > Transaction

[jira] [Commented] (KAFKA-10257) system test kafkatest.tests.core.security_rolling_upgrade_test fails

[ https://issues.apache.org/jira/browse/KAFKA-10257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157500#comment-17157500 ] Jun Rao commented on KAFKA-10257: - [~chia7712] : Yes. Thanks for helping out. > system test

[jira] [Resolved] (KAFKA-10002) Improve performances of StopReplicaRequest with large number of partitions to be deleted

[ https://issues.apache.org/jira/browse/KAFKA-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10002. - Fix Version/s: 2.7.0 Resolution: Fixed merged the PR to trunk > Improve performances of

[jira] [Resolved] (KAFKA-10235) Fix flaky transactions_test.py

[ https://issues.apache.org/jira/browse/KAFKA-10235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10235. - Fix Version/s: 3.0.0 Resolution: Fixed merged the PR to trunk. > Fix flaky transactions_test.py

[jira] [Created] (KAFKA-10257) system test kafkatest.tests.core.security_rolling_upgrade_test fails

Jun Rao created KAFKA-10257: --- Summary: system test kafkatest.tests.core.security_rolling_upgrade_test fails Key: KAFKA-10257 URL: https://issues.apache.org/jira/browse/KAFKA-10257 Project: Kafka

[jira] [Resolved] (KAFKA-10225) Increase default zk session timeout for system tests

[ https://issues.apache.org/jira/browse/KAFKA-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10225. - Fix Version/s: 2.7.0 Resolution: Fixed merged the PR to trunk > Increase default zk session

[jira] [Resolved] (KAFKA-9769) ReplicaManager Partition.makeFollower Increases LeaderEpoch when ZooKeeper disconnect occurs

[ https://issues.apache.org/jira/browse/KAFKA-9769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-9769. Fix Version/s: 2.7.0 Assignee: Andrew Choi Resolution: Fixed merged the PR to trunk >

[jira] [Commented] (KAFKA-9693) Kafka latency spikes caused by log segment flush on roll

[ https://issues.apache.org/jira/browse/KAFKA-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146527#comment-17146527 ] Jun Rao commented on KAFKA-9693: [~joliveirinha]: Thanks for the analysis. To trigger the flush during

[jira] [Commented] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145752#comment-17145752 ] Jun Rao commented on KAFKA-4084: [~hai_lin] : (1) If we just need a tool to disallow a broker from taking

[jira] [Commented] (KAFKA-10197) Elect preferred leader when completing a partition reassignment

[ https://issues.apache.org/jira/browse/KAFKA-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144190#comment-17144190 ] Jun Rao commented on KAFKA-10197: - [~bob-barrett]: Thanks for filing the issue. In

[jira] [Commented] (KAFKA-9693) Kafka latency spikes caused by log segment flush on roll

[ https://issues.apache.org/jira/browse/KAFKA-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143037#comment-17143037 ] Jun Rao commented on KAFKA-9693: [~joliveirinha]: Thanks for the info. I am not sure that we fully

[jira] [Commented] (KAFKA-10191) fix flaky StreamsOptimizedTest

[ https://issues.apache.org/jira/browse/KAFKA-10191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142301#comment-17142301 ] Jun Rao commented on KAFKA-10191: - This test failure occurred 

<    1   2   3   4   5   >