[jira] [Commented] (KAFKA-16092) Queues for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841566#comment-17841566 ] zhangzhisheng commented on KAFKA-16092: --- this new feature is good  > Queues for Kafka >

[jira] [Comment Edited] (KAFKA-16092) Queues for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841566#comment-17841566 ] zhangzhisheng edited comment on KAFKA-16092 at 4/28/24 3:06 AM: this new

[jira] [Updated] (KAFKA-16092) Queues for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-16092: -- Attachment: image-2024-04-28-11-05-56-153.png > Queues for Kafka > > >

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

[ https://issues.apache.org/jira/browse/KAFKA-13636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836455#comment-17836455 ] zhangzhisheng commented on KAFKA-13636: --- Kafka broker version is 2.7.2 Client version is 2.5.2.

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822181#comment-17822181 ] zhangzhisheng commented on KAFKA-3370: --

[jira] [Updated] (KAFKA-16314) Add the new ABORTABLE_ERROR

[ https://issues.apache.org/jira/browse/KAFKA-16314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-16314: -- Attachment: image-2024-02-29-21-43-51-000.png > Add the new ABORTABLE_ERROR >

[jira] [Commented] (KAFKA-16314) Add the new ABORTABLE_ERROR

[ https://issues.apache.org/jira/browse/KAFKA-16314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822138#comment-17822138 ] zhangzhisheng commented on KAFKA-16314: --- I think this ability is needed > Add the new

[jira] [Commented] (KAFKA-12261) Splitting partition causes message loss for consumers with auto.offset.reset=latest

[ https://issues.apache.org/jira/browse/KAFKA-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822135#comment-17822135 ] zhangzhisheng commented on KAFKA-12261: --- It is like this, but in my understanding, this is normal.

[jira] [Comment Edited] (KAFKA-12946) __consumer_offsets topic with very big partitions

[ https://issues.apache.org/jira/browse/KAFKA-12946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17611018#comment-17611018 ] zhangzhisheng edited comment on KAFKA-12946 at 7/21/23 2:15 AM: upgrade

[jira] [Comment Edited] (KAFKA-9964) Better description of RoundRobinPartitioner behavior for AK 2.4+

[ https://issues.apache.org/jira/browse/KAFKA-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744947#comment-17744947 ] zhangzhisheng edited comment on KAFKA-9964 at 7/20/23 8:41 AM: --- it's bug,

[jira] [Commented] (KAFKA-9964) Better description of RoundRobinPartitioner behavior for AK 2.4+

[ https://issues.apache.org/jira/browse/KAFKA-9964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744947#comment-17744947 ] zhangzhisheng commented on KAFKA-9964: -- it's bug, pls follow RoundRobinPartitioner broken by KIP-480

[jira] [Commented] (KAFKA-9965) Uneven distribution with RoundRobinPartitioner in AK 2.4+

[ https://issues.apache.org/jira/browse/KAFKA-9965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744944#comment-17744944 ] zhangzhisheng commented on KAFKA-9965: -- (y) > Uneven distribution with RoundRobinPartitioner in AK

[jira] [Commented] (KAFKA-13303) RoundRobinPartitioner broken by KIP-480

[ https://issues.apache.org/jira/browse/KAFKA-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744943#comment-17744943 ] zhangzhisheng commented on KAFKA-13303: --- its's ture that RoundRobinPartitioner lead to data

[jira] [Updated] (KAFKA-4854) Producer RecordBatch executes callbacks with `null` provided for metadata if an exception is encountered

[ https://issues.apache.org/jira/browse/KAFKA-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-4854: - Attachment: image-2023-03-28-15-45-47-783.png > Producer RecordBatch executes callbacks with

[jira] [Commented] (KAFKA-4854) Producer RecordBatch executes callbacks with `null` provided for metadata if an exception is encountered

[ https://issues.apache.org/jira/browse/KAFKA-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705857#comment-17705857 ] zhangzhisheng commented on KAFKA-4854: -- behavior is intended；   {code:java} // code placeholder  

[jira] [Commented] (KAFKA-9350) IllegalStateException when materializing transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-9350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675543#comment-17675543 ] zhangzhisheng commented on KAFKA-9350: --   kafka version: 2.13_2.7.2 I've found the same error in a

[jira] [Commented] (KAFKA-12946) __consumer_offsets topic with very big partitions

[ https://issues.apache.org/jira/browse/KAFKA-12946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17611018#comment-17611018 ] zhangzhisheng commented on KAFKA-12946: --- upgrade 2.4.2 > __consumer_offsets topic with very big

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

[ https://issues.apache.org/jira/browse/KAFKA-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17561256#comment-17561256 ] zhangzhisheng commented on KAFKA-10888: --- goog job > Sticky partition leads to uneven product

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

[ https://issues.apache.org/jira/browse/KAFKA-13509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511688#comment-17511688 ] zhangzhisheng commented on KAFKA-13509: --- (y) > Support max timestamp in GetOffsetShell >

[jira] [Commented] (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:comment-tabpanel=17511686#comment-17511686 ] zhangzhisheng commented on KAFKA-12541: --- it is very useful(y) > Extend ListOffset to fetch offset

[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=17511576#comment-17511576 ] zhangzhisheng commented on KAFKA-9826: -- [~junrao]  kafka version from 2.4.1 to 2.8.1，the issue has

[jira] [Updated] (KAFKA-13760) Kafka 2.8.1 : log clean skip __consumer__offsets-45

[ https://issues.apache.org/jira/browse/KAFKA-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-13760: -- Description: I upgraded Kafka from 2.12_2.4.1 to 2.13_2.8.1 version. From then,

[jira] [Updated] (KAFKA-13760) Kafka 2.8.1 : log clean skip __consumer__offsets-45

[ https://issues.apache.org/jira/browse/KAFKA-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-13760: -- Description: I upgraded Kafka from 2.12_2.4.1 to 2.13_2.8.1 version. From then,

[jira] [Updated] (KAFKA-13760) Kafka 2.8.1 : log clean skip __consumer__offsets-45

[ https://issues.apache.org/jira/browse/KAFKA-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-13760: -- Description: I upgraded Kafka from 2.12_2.4.1 to 2.13_2.8.1 version. From then,

[jira] [Updated] (KAFKA-13760) Kafka 2.8.1 : log clean skip __consumer__offsets-45

[ https://issues.apache.org/jira/browse/KAFKA-13760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-13760: -- Description: I upgraded Kafka from 2.12_2.4.1 to 2.13_2.8.1 version. From then,

[jira] [Created] (KAFKA-13760) Kafka 2.8.1 : log clean skip __consumer__offsets-45

zhangzhisheng created KAFKA-13760: - Summary: Kafka 2.8.1 : log clean skip __consumer__offsets-45 Key: KAFKA-13760 URL: https://issues.apache.org/jira/browse/KAFKA-13760 Project: Kafka Issue

[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=17342571#comment-17342571 ] zhangzhisheng commented on KAFKA-9826: -- we have same problems，kafka version 2.12_2.4.1 {code:java}

[jira] [Comment Edited] (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=17241383#comment-17241383 ] zhangzhisheng edited comment on KAFKA-3042 at 12/3/20, 8:27 AM: using

[jira] [Comment Edited] (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=17241383#comment-17241383 ] zhangzhisheng edited comment on KAFKA-3042 at 12/3/20, 8:26 AM: using

[jira] [Comment Edited] (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=17241383#comment-17241383 ] zhangzhisheng edited comment on KAFKA-3042 at 12/3/20, 8:25 AM: using

[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=17241383#comment-17241383 ] zhangzhisheng commented on KAFKA-3042: -- using kafka_2.12-2.4.1，zookeeper-3.5.7 3 ZKs 3 Broker

[jira] [Commented] (KAFKA-6666) OffsetOutOfRangeException: Replica Thread Stopped Resulting in Underreplicated Partitions

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130030#comment-17130030 ] zhangzhisheng commented on KAFKA-: -- on our prd cluster, one topic partition ReplicaFetcherThread

[jira] [Comment Edited] (KAFKA-6666) OffsetOutOfRangeException: Replica Thread Stopped Resulting in Underreplicated Partitions

[ https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130030#comment-17130030 ] zhangzhisheng edited comment on KAFKA- at 6/10/20, 3:51 AM: on our

[jira] [Commented] (KAFKA-7689) Add Commit/List Offsets Operations to AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086181#comment-17086181 ] zhangzhisheng commented on KAFKA-7689: -- good   > Add Commit/List Offsets Operations to AdminClient

[jira] [Commented] (KAFKA-6834) log cleaner should handle the case when the size of a message set is larger than the max message size

[ https://issues.apache.org/jira/browse/KAFKA-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035922#comment-17035922 ] zhangzhisheng commented on KAFKA-6834: -- kafka2.12_0.11.0.3 log clean tread stoped，throw exception

[jira] [Comment Edited] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014807#comment-17014807 ] zhangzhisheng edited comment on KAFKA-6762 at 1/14/20 2:31 AM: --- This

[jira] [Commented] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014807#comment-17014807 ] zhangzhisheng commented on KAFKA-6762: -- This happens in our production env which version is

[jira] [Updated] (KAFKA-9136) get consumer latest commited timestamp

[ https://issues.apache.org/jira/browse/KAFKA-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-9136: - Description: for example，i have two topics，one_topic、two_topic，each topic have two

[jira] [Updated] (KAFKA-9136) get consumer latest commited timestamp

[ https://issues.apache.org/jira/browse/KAFKA-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-9136: - Description: for example，i have two topics，one_topic、two_topic，each topic have two

[jira] [Commented] (KAFKA-9136) get consumer latest commited timestamp

[ https://issues.apache.org/jira/browse/KAFKA-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966635#comment-16966635 ] zhangzhisheng commented on KAFKA-9136: -- {code:java} // code placeholder {code} public static long

[jira] [Issue Comment Deleted] (KAFKA-9136) get consumer latest commited timestamp

[ https://issues.apache.org/jira/browse/KAFKA-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-9136: - Comment: was deleted (was: {code:java} // code placeholder {code} public static long

[jira] [Updated] (KAFKA-9136) get consumer latest commited timestamp

[ https://issues.apache.org/jira/browse/KAFKA-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-9136: - Description: for example，i have two topics，one_topic、two_topic，each topic have two

[jira] [Updated] (KAFKA-9136) get consumer latest commited timestamp

[ https://issues.apache.org/jira/browse/KAFKA-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-9136: - Description: for example，i have two topics，one_topic、two_topic，each topic have two

[jira] [Updated] (KAFKA-9136) get consumer latest commited timestamp

[ https://issues.apache.org/jira/browse/KAFKA-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangzhisheng updated KAFKA-9136: - Description: topic > get consumer latest commited timestamp >

[jira] [Created] (KAFKA-9136) get consumer latest commited timestamp

zhangzhisheng created KAFKA-9136: Summary: get consumer latest commited timestamp Key: KAFKA-9136 URL: https://issues.apache.org/jira/browse/KAFKA-9136 Project: Kafka Issue Type: Wish

[jira] [Commented] (KAFKA-7625) Kafka Broker node JVM crash - kafka.coordinator.transaction.TransactionCoordinator.$anonfun$handleEndTransaction

[ https://issues.apache.org/jira/browse/KAFKA-7625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928853#comment-16928853 ] zhangzhisheng commented on KAFKA-7625: -- we has the crash case in 2.12.0.11.0.2 version and