[
https://issues.apache.org/jira/browse/KAFKA-19331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18052215#comment-18052215
]
Abhijit edited comment on KAFKA-19331 at 1/15/26 8:46 PM:
----------------------------------------------------------
Hi [~showuon]
Since there has been no recent activity on this issue, I’m assigning the task
to myself. I’ve started contributing to Apache Kafka and identified this as a
problem that I believe is suitable for me to work on.
I’ve already created a PR addressing the issue, and I’m assigning it to myself
now (apologies for doing this directly). My intention is to avoid any confusion
or duplicate effort from other new contributors who might otherwise start
working on the same unassigned issue.
was (Author: JIRAUSER312005):
[~showuon] I am assigning this task to myself, I’ve started contributing to
Apache Kafka and found a problem that I believe is suitable for me to work on.
Please let me know if there are any concerns.
> No error handling for leader not appeared in applyLocalFollowersDelta
> ----------------------------------------------------------------------
>
> Key: KAFKA-19331
> URL: https://issues.apache.org/jira/browse/KAFKA-19331
> Project: Kafka
> Issue Type: Bug
> Reporter: Luke Chen
> Assignee: Abhijit
> Priority: Major
> Labels: newbie
>
> In ReplicaManager#applyLocalFollowersDelta, when we prepare for fetching from
> the leader, we'll check if the leader node info is in metadata image. If
> somehow it didn't include in the newImage, we'll log something like:
>
> {code:java}
> [2025-05-26 15:25:58,124] TRACE [Broker id=4] Unable to start fetching
> quickstart-events-0 with topic ID Some(Dn9K0BB8QWuj4PqcJD0nrA) from leader
> Some(2) because it is not alive. (state.change.logger)
> [2025-05-26 15:25:58,124] INFO [Broker id=4] Started fetchers as part of
> become-follower for 1 partitions (state.change.logger)
> {code}
>
> It's confusing to users to see it's unable to fetch, then start fetch. And in
> the end, it's not actually fetching... We should handling the error well by
> updating the `FailedPartition` and not updating other successful result
> status.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
