You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2014/12/04 06:02:12 UTC
[jira] [Comment Edited] (KAFKA-1796) Sanity check partition command
line tools
[ https://issues.apache.org/jira/browse/KAFKA-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233913#comment-14233913 ]
Neha Narkhede edited comment on KAFKA-1796 at 12/4/14 5:01 AM:
---------------------------------------------------------------
[~guozhang], KAFKA-1678 is the umbrella JIRA for all the improvements. It will be great if you can take a quick look and review it. See if you'd like to add anything to it.
was (Author: nehanarkhede):
[~guozhang], Here is the umbrella JIRA for all the improvements. It will be great if you can take a quick look and review it. See if you'd like to add anything to it.
> Sanity check partition command line tools
> -----------------------------------------
>
> Key: KAFKA-1796
> URL: https://issues.apache.org/jira/browse/KAFKA-1796
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Labels: newbie
> Fix For: 0.8.3
>
>
> We need to sanity check the input json has the valid values before triggering the admin process. For example, we have seen a scenario where the json input for partition reassignment tools have partition replica info as {broker-1, broker-1, broker-2} and it is still accepted in ZK and eventually lead to under replicated count, etc. This is partially because we use a Map rather than a Set reading the json input for this case; but in general we need to make sure the input parameters like Json needs to be valid before writing it to ZK.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)