[
https://issues.apache.org/jira/browse/KAFKA-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1032:
---------------------------
Fix Version/s: (was: 0.8.1)
0.9.0
> Messages sent to the old leader will be lost on broker GC resulted failure
> --------------------------------------------------------------------------
>
> Key: KAFKA-1032
> URL: https://issues.apache.org/jira/browse/KAFKA-1032
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Fix For: 0.9.0
>
> Attachments: KAFKA-1032.v1.patch
>
>
> As pointed out by Swapnil, today when a broker in on long GC, it will marked
> by the controller as failed and trigger the onBrokerFailure function to
> migrate leadership to other brokers. However, since the Controller does not
> notify the broker with stopReplica request even after a new leader has been
> elected for its partitions. The new leader will hence stop fetching from the
> old leader while the old leader is not aware that he is no longer the leader.
> And since the old leader is not really dead producers will not refresh their
> metadata immediately and will continue sending messages to the old leader.
> The old leader will only know it is no longer the leader when it gets
> notified by controller in the onBrokerStartup function, and message sent
> starting from the time the new leader is elected to the timestamp the old
> leader realize it is no longer the leader will be lost.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
