You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Mayuresh Gharat (JIRA)" <ji...@apache.org> on 2015/02/13 02:08:13 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=14319346#comment-14319346 ] 

Mayuresh Gharat edited comment on KAFKA-1796 at 2/13/15 1:07 AM:
-----------------------------------------------------------------

[~nehanarkhede], I went over KAFKA-1678. It did not find any mention of this issue. May be I missed it. Should this be included in that jira? If no, I can give a shot at this one.


was (Author: mgharat):
[~nehanarkhede], I went over KAFKA-1678. I did not find any mention of this issue. May be I missed it. Should this be included in that jira? If no, I can give a shot at this one.

> 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
>            Assignee: Mayuresh Gharat
>              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)