[
https://issues.apache.org/jira/browse/KAFKA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-43:
-------------------------------
Attachment: kafka-43-v1.patch
Added the ability to move the leader to the preferred replica for a partition.
This patch contains the following changes -
1. A new admin command PreferredReplicaLeaderElectionCommand and corresponding
bin script
2. The admin command takes list of partitions as an input json file and writes
it to the zookeeper persistent path /admin/preferred_replica_election
3. The controller registers a data change listener on the admin path. For each
such partition, it triggers the OnlinePartition -> OnlinePartition state change
with the preferred replica election leader selector. It batches the state
changes for all partitions to be able to batch the leader and isr requests sent
to the brokers. This is done since there is a very high chance that the admin
might use this feature to move some leaders to a particular broker. The
controller deletes the admin path once it has finished processing all partitions
4. Added 2 new unit tests to AdminTest
> Rebalance to preferred broke with intra-cluster replication support
> -------------------------------------------------------------------
>
> Key: KAFKA-43
> URL: https://issues.apache.org/jira/browse/KAFKA-43
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jun Rao
> Assignee: Neha Narkhede
> Priority: Blocker
> Labels: features
> Fix For: 0.8
>
> Attachments: kafka-43-v1.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> We need to allow the leader to be moved to the preferred broker, for better
> load balancing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
