Is there a configuration parameter in storm so that a topology will still be displayed after it is killed ?
Thank you
No, there is no configuration parameter for this. After a Storm topology is killed, it is removed from the Storm UI. According to Storm's documentation, the Storm UI is only for monitoring "running topologies." See the bottom of the page at https://storm.apache.org/documentation/Running-topologies-on-a-production-cluster.html
Related
I'm unable to view the topology summary in Storm UI (in Ambari). The UI gets hang with "Loading Topology Summary" message. Please help me out to resolve this issue.
Ambari version : 2.6.0.0
HDP: 2.6.3.0
Storm : 1.1.0
Regards,
Naresh.
Here is the Image
I too ran across this recently. Turns out the metadata stored in ZK was out of date with the Broker IDs. You can read more about it and how to resolve it here: https://community.hortonworks.com/articles/197972/storm-ui-hung-with-loading-topology-summary.html
Looks like your storm state is not updated in the zookeeper. Try cleaning the current storm states from zookeeper and then restart storm from ambari UI.
I deploy a storm cluster with version 1.0.2. There is a case as below:
A topology is created and is submitted on the cluster to do some analysis for one client/customer. When another client also needs the same analysis, as I think, the similar bolts can be created and append the spout in the topology. I wonder if it's possible to create such bolts when the topology is running. That means the running analysis for the first client can't be interrupted. Is it possible?
Thanks for your any comments.
Max
Altering a running topology is not possible. You need to kill the topology and re-submit it with the newly added bolt.
Is it possible to change the topology layout while it is running? I would like to change the stream groupings and bolts while it is active.
Submitting the yaml file with the new topology layout says it cannot deploy since it is already running.
I'm using Apache Storm 0.10.0
Thanks
It is not possible to change the structure of a topology while it is running. You need to kill the topology and redeploy the new version afterwards.
The only parameter you can change while a topology is running it the parallelism. See here for more details:
V 2.0.0 - https://storm.apache.org/releases/2.0.0/Understanding-the-parallelism-of-a-Storm-topology.html
This time, we build a storm cluster and don't have a tool like cloudera manager to monitor the status of cluster except the storm ui, and send alert notice when the cluster is in bad status.
Please write linux scripts with some basic storm commands and zookeeper commands to ensure the health of your cluster.
I am developing a storm topology locally. I am using the Storm 0.9.2-incubating and have developed a simple Topology. When I deploy it using the LocalCluster() option, it works fine, but it will not show up in my Storm UI it just executes.
When I deploy it regularly, it will show the Topology in my Storm UI, but no spouts or bolts will be visible when I click it.
I have also tried this with example WordCountTopology that comes in many storm starter projects. The same behavior happens.
My question is really, why are the spouts and bolts not showing up? If you deploy a topology locally without using LocalCluser() option will that cause problems? Is it possible to deploy a topology on my local box and see it in Storm UI with all the spouts and bolts and not have it execute immediately, but wait for something such as a kafka message?
Are you running Storm Supervisor? If you deploy a new topology and Supervisor isn't running the topology will show up in the UI but since its never initialized it doesn't show any stats when you click into it.