[
https://issues.apache.org/jira/browse/KAFKA-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596716#comment-13596716
]
Neha Narkhede commented on KAFKA-795:
-------------------------------------
1. That's a good idea
2. The tool should protect against overwrite of a zookeeper path in progress by
the controller. So one strategy could be let the tool throw an error if there
is a zookeeper path already created. The controller, on the other hand, should
ensure that it deletes that path when it has completed processing it,
successfully or unsuccessfully.
3. This is not possible since there is no way for the tool to know what's in
the controller's log. This is something that the admin has to do on his/her own.
> Improvements to PreferredReplicaLeaderElection tool
> ---------------------------------------------------
>
> Key: KAFKA-795
> URL: https://issues.apache.org/jira/browse/KAFKA-795
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Swapnil Ghike
> Assignee: Swapnil Ghike
> Labels: kafka-0.8, p2
> Fix For: 0.8
>
>
> We can make some improvements to the PreferredReplicaLeaderElection tool:
> 1. Terminate the tool if a controller is not up and running. Currently we can
> run the tool without having any broker running, which is kind of confusing.
> 2. Should we delete /admin zookeeper path in PreferredReplicaLeaderElection
> (and ReassignPartition) tool at the end? Otherwise the next run of the tool
> complains that a replica election is already in progress.
> 3. If there is an error, we can see it in cotroller.log. Should the tool also
> throw an error?
--
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
