[
https://issues.apache.org/jira/browse/KAFKA-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18122133#comment-18122133
]
Tom Thornton edited comment on KAFKA-18715 at 10/2/26 11:30 PM:
----------------------------------------------------------------
https://github.com/apache/kafka/pull/23680
was (Author: JIRAUSER307823):
[~jhooper] we (Slack) ran into an issue with our Kafka deployment where having
an Aggressive strategy would have elected the best replica automatically. I
noticed that part of this was
[implemented|https://github.com/apache/kafka/pull/20371] and later
[reverted|https://github.com/apache/kafka/pull/20371]. I published a
[PR|https://github.com/apache/kafka/pull/23680] that takes a smaller approach:
instead of pulling the replica info from brokers (new RPC) it adds in
leaderless partition info (log end offset, last epoch) to the heartbeats
already pushed to controllers regularly. Since push differs from the original
proposal, I'm happy to update the KIP or raise this in the email discussion,
let me know what you think. Thanks!
> Unclean Recovery: Aggressive strategy
> -------------------------------------
>
> Key: KAFKA-18715
> URL: https://issues.apache.org/jira/browse/KAFKA-18715
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Jonah Hooper
> Assignee: Jonah Hooper
> Priority: Major
> Labels: Phase-3
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Implement the unclean recovery aggressive strategy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
