[jira] [Comment Edited] (KAFKA-17340) Kafka Java sdk ConsumerConfig describe doc is incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-17340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873511#comment-17873511 ] shilin Lu edited comment on KAFKA-17340 at 8/14/24 12:00 PM: -

[jira] [Commented] (KAFKA-17340) Kafka Java sdk ConsumerConfig describe doc is incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-17340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873511#comment-17873511 ] shilin Lu commented on KAFKA-17340: --- commit a pr for this issue: [https://github.com/a

[jira] [Assigned] (KAFKA-17305) Quorum controller should check the finalized kraft.version during broker registration

[ https://issues.apache.org/jira/browse/KAFKA-17305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shilin Lu reassigned KAFKA-17305: - Assignee: shilin Lu (was: Alyssa Huang) > Quorum controller should check the finalized kraft.v

[jira] [Created] (KAFKA-17340) Kafka Java sdk ConsumerConfig describe doc is incorrectly

shilin Lu created KAFKA-17340: - Summary: Kafka Java sdk ConsumerConfig describe doc is incorrectly Key: KAFKA-17340 URL: https://issues.apache.org/jira/browse/KAFKA-17340 Project: Kafka Issue Ty

[jira] [Commented] (KAFKA-13639) NotEnoughReplicasException for __consumer_offsets topic due to out of order offset

[ https://issues.apache.org/jira/browse/KAFKA-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774633#comment-17774633 ] shilin Lu commented on KAFKA-13639: --- i found this problem in kafka 0.11.0.3 > NotEnou

[jira] [Commented] (KAFKA-13639) NotEnoughReplicasException for __consumer_offsets topic due to out of order offset

[ https://issues.apache.org/jira/browse/KAFKA-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774631#comment-17774631 ] shilin Lu commented on KAFKA-13639: --- is there any progress for this issue?  [~ijuma] 

[jira] [Commented] (KAFKA-15240) BrokerToControllerChannelManager cache activeController error cause DefaultAlterPartitionManager send AlterPartition request failed

[ https://issues.apache.org/jira/browse/KAFKA-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752604#comment-17752604 ] shilin Lu commented on KAFKA-15240: --- [~cmccabe] [~hachikuji] please take a look at thi

[jira] [Commented] (KAFKA-15240) BrokerToControllerChannelManager cache activeController error cause DefaultAlterPartitionManager send AlterPartition request failed

[ https://issues.apache.org/jira/browse/KAFKA-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746980#comment-17746980 ] shilin Lu commented on KAFKA-15240: --- [~guozhang]  > BrokerToControllerChannelManager

[jira] [Commented] (KAFKA-15240) BrokerToControllerChannelManager cache activeController error cause DefaultAlterPartitionManager send AlterPartition request failed

[ https://issues.apache.org/jira/browse/KAFKA-15240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746733#comment-17746733 ] shilin Lu commented on KAFKA-15240: --- [~ijuma] [~junrao] please watch this issue，thank

[jira] [Created] (KAFKA-15240) BrokerToControllerChannelManager cache activeController error cause DefaultAlterPartitionManager send AlterPartition request failed

shilin Lu created KAFKA-15240: - Summary: BrokerToControllerChannelManager cache activeController error cause DefaultAlterPartitionManager send AlterPartition request failed Key: KAFKA-15240 URL: https://issues.apache.

[jira] [Commented] (KAFKA-9903) kafka ShutdownableThread judge thread isRuning status has some bug

[ https://issues.apache.org/jira/browse/KAFKA-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090355#comment-17090355 ] shilin Lu commented on KAFKA-9903: -- [~guozhang] [~ijuma] > kafka ShutdownableThread ju

[jira] [Commented] (KAFKA-9903) kafka ShutdownableThread judge thread isRuning status has some bug

[ https://issues.apache.org/jira/browse/KAFKA-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089973#comment-17089973 ] shilin Lu commented on KAFKA-9903: -- pull request: [https://github.com/apache/kafka/pull/

[jira] [Commented] (KAFKA-9903) kafka ShutdownableThread judge thread isRuning status has some bug

[ https://issues.apache.org/jira/browse/KAFKA-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089936#comment-17089936 ] shilin Lu commented on KAFKA-9903: -- ok, i think your advice is make sense. i will create

[jira] [Commented] (KAFKA-9903) kafka ShutdownableThread judge thread isRuning status has some bug

[ https://issues.apache.org/jira/browse/KAFKA-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089688#comment-17089688 ] shilin Lu commented on KAFKA-9903: -- [~guozhang] [~ijuma] please take a look at this issu

[jira] [Created] (KAFKA-9903) kafka ShutdownableThread judge thread isRuning status has some bug

shilin Lu created KAFKA-9903: Summary: kafka ShutdownableThread judge thread isRuning status has some bug Key: KAFKA-9903 URL: https://issues.apache.org/jira/browse/KAFKA-9903 Project: Kafka Is

[jira] [Commented] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984230#comment-16984230 ] shilin Lu commented on KAFKA-9156: -- [~amironov] Thanks for comment.this days i am upgra

[jira] [Comment Edited] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969820#comment-16969820 ] shilin Lu edited comment on KAFKA-9156 at 11/8/19 5:07 AM: --- [~g

[jira] [Commented] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969820#comment-16969820 ] shilin Lu commented on KAFKA-9156: -- [~guozhang] i think only use val AtomicReference can

[jira] [Issue Comment Deleted] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shilin Lu updated KAFKA-9156: - Comment: was deleted (was: [~guozhang] as you suggest use val AtomicReference in this case ,i think it c

[jira] [Comment Edited] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969794#comment-16969794 ] shilin Lu edited comment on KAFKA-9156 at 11/8/19 3:27 AM: --- [~g

[jira] [Comment Edited] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969794#comment-16969794 ] shilin Lu edited comment on KAFKA-9156 at 11/8/19 3:27 AM: --- [~g

[jira] [Commented] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969794#comment-16969794 ] shilin Lu commented on KAFKA-9156: -- [~guozhang] as you suggest use val AtomicReference i

[jira] [Comment Edited] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969794#comment-16969794 ] shilin Lu edited comment on KAFKA-9156 at 11/8/19 3:24 AM: --- [~g

[jira] [Commented] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969747#comment-16969747 ] shilin Lu commented on KAFKA-9156: -- [~guozhang] thanks for reply. i will fix it and prov

[jira] [Updated] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shilin Lu updated KAFKA-9156: - Reviewer: Ismael Juma > LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent > stat

[jira] [Commented] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969107#comment-16969107 ] shilin Lu commented on KAFKA-9156: -- [~guozhang] [~ijuma] please take a look at this issu

[jira] [Created] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state

shilin Lu created KAFKA-9156: Summary: LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state Key: KAFKA-9156 URL: https://issues.apache.org/jira/browse/KAFKA-9156 Project: Kafka

[jira] [Commented] (KAFKA-8801) electLeaderForPartitions redundancy for some success elect partitions

[ https://issues.apache.org/jira/browse/KAFKA-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907767#comment-16907767 ] shilin Lu commented on KAFKA-8801: -- [~junrao] please take a look at this issue, thank yo

[jira] [Created] (KAFKA-8801) electLeaderForPartitions redundancy for some success elect partitions

shilin Lu created KAFKA-8801: Summary: electLeaderForPartitions redundancy for some success elect partitions Key: KAFKA-8801 URL: https://issues.apache.org/jira/browse/KAFKA-8801 Project: Kafka

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728626#comment-16728626 ] Shilin Lu commented on KAFKA-4477: -- hello, we meet the same problem in our prod environm

[jira] [Comment Edited] (KAFKA-5778) Kafka cluster is not responding when one broker hangs and resulted in too many connections in close_wait in other brokers

[ https://issues.apache.org/jira/browse/KAFKA-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728624#comment-16728624 ] Shilin Lu edited comment on KAFKA-5778 at 12/25/18 8:44 AM: h

[jira] [Commented] (KAFKA-5778) Kafka cluster is not responding when one broker hangs and resulted in too many connections in close_wait in other brokers

[ https://issues.apache.org/jira/browse/KAFKA-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728624#comment-16728624 ] Shilin Lu commented on KAFKA-5778: -- hello, we meet the same problem in our prod environm