You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Nick Allen (JIRA)" <ji...@apache.org> on 2017/09/13 12:53:00 UTC

[jira] [Commented] (METRON-1093) Start/stop/restart topologies use Storm CLI

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

Nick Allen commented on METRON-1093:
------------------------------------

IMHO, the fix here is a work around for us not controlling the shutdown order of components.  I would suggest that METRON-1177 is a better solution to the problem.

https://issues.apache.org/jira/browse/METRON-1177
https://github.com/apache/metron/pull/748

> Start/stop/restart topologies use Storm CLI
> -------------------------------------------
>
>                 Key: METRON-1093
>                 URL: https://issues.apache.org/jira/browse/METRON-1093
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: David M. Lyle
>
> Currently both Ambari status check and Ambari Start/Stop/Restart topologies use Storm REST to get the status of the topologies. This can lead to an inaccurate status when the topologies are running and the Storm UI is not. During an Ambari restart, the topologies wouldn't be restarted when this occurs.
> Ambari needs status check to be quick, so continue to use Storm REST. Modify start/stop/restart to get the running topologies via the Storm CLI.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)