[GitHub] [kafka] dongjinleekr commented on pull request #11579: KAFKA-13518: Update gson dependency

dongjinleekr commented on pull request #11579: URL: https://github.com/apache/kafka/pull/11579#issuecomment-1000985229 Hi @showuon, Here it is. I just updated the issue title more clearly and updated the spotbugs dependency into 4.5.2. -- This is an automated message from the

[jira] [Updated] (KAFKA-13518) Update gson dependency

[ https://issues.apache.org/jira/browse/KAFKA-13518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjin Lee updated KAFKA-13518: Summary: Update gson dependency (was: Update gson and netty-codec in 3.0.0) > Update gson

[jira] [Commented] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17465121#comment-17465121 ] Luke Chen commented on KAFKA-13564: --- [~polaris.alioth] , it looks like the expected leader broker

[GitHub] [kafka] dengziming closed pull request #11626: MINOR: Ensure AlterIsr is forwarded to Controller in KRaft

dengziming closed pull request #11626: URL: https://github.com/apache/kafka/pull/11626 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[GitHub] [kafka] jlprat commented on pull request #11518: MINOR: Upgrade to Gradle 7.3.3

jlprat commented on pull request #11518: URL: https://github.com/apache/kafka/pull/11518#issuecomment-1000867376 Test failures should be unrelated to the change -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[GitHub] [kafka] jlprat closed pull request #11518: MINOR: Upgrade to Gradle 7.3.3

jlprat closed pull request #11518: URL: https://github.com/apache/kafka/pull/11518 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[jira] [Comment Edited] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464929#comment-17464929 ] ZhenChun Pan edited comment on KAFKA-13564 at 12/24/21, 12:22 PM: --

[jira] [Updated] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhenChun Pan updated KAFKA-13564: - Description: The machine of broker0 dropped, and some partition change the leader to broker1.

[jira] [Updated] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhenChun Pan updated KAFKA-13564: - Description: The machine of broker0 dropped, and some partition change the leader to broker1.

[jira] [Updated] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhenChun Pan updated KAFKA-13564: - Attachment: part_of_controller.log.txt part_of_server.log.txt

[jira] [Commented] (KAFKA-13374) [Docs] - All reads from the leader of the partition even after KIP-392?

[ https://issues.apache.org/jira/browse/KAFKA-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464999#comment-17464999 ] ASF GitHub Bot commented on KAFKA-13374: jaceklaskowski commented on pull request #391: URL:

[GitHub] [kafka] vamossagar12 commented on pull request #11211: KAFKA-12960: Enforcing strict retention time for WindowStore and Sess…

vamossagar12 commented on pull request #11211: URL: https://github.com/apache/kafka/pull/11211#issuecomment-1000772352 > Hey @vamossagar12 sorry for the long silence, I've been in a crunch to finish a project by the end of the year. I'll make a pass on all the open PRs I've been

[GitHub] [kafka] vamossagar12 commented on pull request #11424: KAFKA-13152: Replace "buffered.records.per.partition" with "input.buffer.max.bytes"

vamossagar12 commented on pull request #11424: URL: https://github.com/apache/kafka/pull/11424#issuecomment-1000771278 > > Thanks @guozhangwang . I had one question on the changes suggested by you. > > Just replied on your question. LMK if that works or not. Yeah it does..

[GitHub] [kafka] vamossagar12 commented on a change in pull request #11424: KAFKA-13152: Replace "buffered.records.per.partition" with "input.buffer.max.bytes"

vamossagar12 commented on a change in pull request #11424: URL: https://github.com/apache/kafka/pull/11424#discussion_r774963827 ## File path: streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java ## @@ -1224,17 +1248,20 @@ private int getNextThreadIndex() {

[GitHub] [kafka] vamossagar12 commented on a change in pull request #11424: KAFKA-13152: Replace "buffered.records.per.partition" with "input.buffer.max.bytes"

vamossagar12 commented on a change in pull request #11424: URL: https://github.com/apache/kafka/pull/11424#discussion_r774963698 ## File path: streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java ## @@ -1074,9 +1083,22 @@ private static Metrics getMetrics(final

[GitHub] [kafka] jlprat commented on pull request #11518: MINOR: Upgrade to Gradle 7.3.3

jlprat commented on pull request #11518: URL: https://github.com/apache/kafka/pull/11518#issuecomment-1000770093 As I updated the title of the PR, it seems that the `stage/Build/ARM` build failed. I'll try to close and open again the PR to re-trigger a build if all the others are fine.

[GitHub] [kafka] jlprat commented on pull request #11518: MINOR: Upgrade to Gradle 7.3.3

jlprat commented on pull request #11518: URL: https://github.com/apache/kafka/pull/11518#issuecomment-1000769090 Since I opened the PR, a couple of patch versions have been released, I updated this PR to use the latest gradle version `7.3.3`. -- This is an automated message from the

[jira] [Commented] (KAFKA-9800) [KIP-580] Client Exponential Backoff Implementation

[ https://issues.apache.org/jira/browse/KAFKA-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464944#comment-17464944 ] Luke Chen commented on KAFKA-9800: -- Creating 3 sub-tasks for this KIP, and co-authored with [~d8tltanc]

[jira] [Created] (KAFKA-13567) adminClient exponential backoff implementation

Luke Chen created KAFKA-13567: - Summary: adminClient exponential backoff implementation Key: KAFKA-13567 URL: https://issues.apache.org/jira/browse/KAFKA-13567 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-13566) producer exponential backoff implementation

Luke Chen created KAFKA-13566: - Summary: producer exponential backoff implementation Key: KAFKA-13566 URL: https://issues.apache.org/jira/browse/KAFKA-13566 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-13565) consumer exponential backoff implementation

Luke Chen created KAFKA-13565: - Summary: consumer exponential backoff implementation Key: KAFKA-13565 URL: https://issues.apache.org/jira/browse/KAFKA-13565 Project: Kafka Issue Type: Sub-task

[jira] [Assigned] (KAFKA-9800) [KIP-580] Client Exponential Backoff Implementation

[ https://issues.apache.org/jira/browse/KAFKA-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen reassigned KAFKA-9800: Assignee: Luke Chen (was: Cheng Tan) > [KIP-580] Client Exponential Backoff Implementation >

[jira] [Comment Edited] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464929#comment-17464929 ] ZhenChun Pan edited comment on KAFKA-13564 at 12/24/21, 8:50 AM: -

[jira] [Comment Edited] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464929#comment-17464929 ] ZhenChun Pan edited comment on KAFKA-13564 at 12/24/21, 8:50 AM: -

[jira] [Updated] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhenChun Pan updated KAFKA-13564: - Description: The machine of broker0 dropped, and some partition change the leader to broker1.

[jira] [Updated] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhenChun Pan updated KAFKA-13564: - Description: The machine of broker0 dropped, and some partition change the leader to broker1.

[jira] [Commented] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464929#comment-17464929 ] ZhenChun Pan commented on KAFKA-13564: -- I add some log imformation about the topic partition

[jira] [Updated] (KAFKA-13564) Kafka keep print NOT_LEADER_OR_FOLLOWER in log file after one broker dropped, and the producer can not work.

[ https://issues.apache.org/jira/browse/KAFKA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhenChun Pan updated KAFKA-13564: - Description: The machine of broker0 dropped, and some partition change the leader to broker1.