[ 
https://issues.apache.org/jira/browse/STORM-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469414#comment-15469414
 ] 

Kamal edited comment on STORM-1985 at 9/7/16 3:40 AM:
------------------------------------------------------

Thanks for the input and sorry for the delay from my side as some travel came 
up for me.

Please review the pull request
https://github.com/apache/storm/pull/1677

Hope it is correct as I have created it first time.

Also please suggest in case we need to implement more admin commands.




was (Author: bkamal):
Thanks for this input and sorry for the delay from my side as some travel came 
up for me.

Please review the pull request
https://github.com/apache/storm/pull/1677

Hope it is correct as I have created it first time.

Also please suggest in case we need to implement more admin commands.



> Provide a tool for showing and killing corrupted topology
> ---------------------------------------------------------
>
>                 Key: STORM-1985
>                 URL: https://issues.apache.org/jira/browse/STORM-1985
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>            Reporter: Jungtaek Lim
>            Assignee: Kamal
>              Labels: newbie
>         Attachments: AdminCommands.java, proposal_admin_tool_design.docx
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After STORM-1976, Nimbus doesn't clean up corrupted topologies.
> (corrupted topology means the topology whose codes are not available on 
> blobstore.)
> Also after STORM-1977, no Nimbus is gaining leadership if one or more 
> topologies are corrupted, which means all nimbuses will be no-op.
> So we should provide a tool to kill specific topology without accessing 
> leader nimbus (because there's no leader nimbus at that time). The tool 
> should also determine which topologies are corrupted, and show its list or 
> clean up automatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to