[
https://issues.apache.org/jira/browse/METRON-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149019#comment-16149019
]
Anand Subramanian edited comment on METRON-1093 at 8/31/17 2:03 PM:
--------------------------------------------------------------------
Due to this issue, some of the storm topologies end up running post-kerberos.
Because of this, some of the topologies would throw authentication errors,
since they are stale and haven't been killed/redeployed. Indices might not be
generated if the indexing topology were not restarted for e.g.
Another side effect also seen is that Management UI reports the status of the
sensors incorrectly. The sensors would show up as stopped, while the actual
status is running.
was (Author: anandsubbu):
Due to this issue, some of the storm topologies end up as still running
post-kerberos. Because of this, some of the topologies would throw
authentication errors, since they are stale and haven't been killed/redeployed.
Another side effect also seen is that Management UI reports the status of the
sensors incorrectly. The sensors would show up as stopped, while the actual
status is running.
> 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)
