[
https://issues.apache.org/jira/browse/KAFKA-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274995#comment-15274995
]
ASF GitHub Bot commented on KAFKA-3670:
---------------------------------------
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/1338
KAFKA-3670; ControlledShutdownLeaderSelector should pick the preferred
replica as the new leader, if possible
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka
kafka-3670-controlled-shutdown-leader-selector-preferred-replica
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1338.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1338
----
commit 1660eae6c3554f2f5b898bf326e3a2c769480f36
Author: Ismael Juma <[email protected]>
Date: 2016-05-07T00:58:45Z
ControlledShutdownLeaderSelector should pick the preferred replica as the
new leader, if possible
----
> ControlledShutdownLeaderSelector should pick the preferred replica as the new
> leader, if possible
> -------------------------------------------------------------------------------------------------
>
> Key: KAFKA-3670
> URL: https://issues.apache.org/jira/browse/KAFKA-3670
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jun Rao
> Assignee: Ismael Juma
> Fix For: 0.10.0.0
>
>
> Currently, ControlledShutdownLeaderSelector selects an arbitrary in-sync
> replica as the new leader. This means that leader can change again to the
> preferred replica very quickly. It's better for
> ControlledShutdownLeaderSelector to select the preferred replica as the new
> leader, if it's in sync.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
