Database Reference
In-Depth Information
$ ./bin/storm jar \
> streaming-chapter-5-1-shaded.jar \
> wiley.streaming.storm.ExampleTopology
246 [main] INFO backtype.storm.StormSubmitter
- Jar not uploaded to master yet. Submitting jar...
346 [main] INFO backtype.storm.StormSubmitter -
Uploading topology
jar streaming-chapter-5-1-shaded.jar to
assigned location: storm-local/nimbus/inbox/
stormjar-18e1fded
-074d-4e51-a2b1-5c98b2e133a6.jar
1337 [main] INFO backtype.storm.StormSubmitter -
Successfully uploaded
topology jar to assigned location:
storm-local/nimbus/inbox/stormjar-18e1fded-074d
-4e51-a2b1-5c98b2e133a6.jar
1338 [main] INFO backtype.storm.StormSubmitter -
Submitting topology
my-topology in distributed mode with conf {}
After a Topology has been submitted, it can be stopped using the Storm
command-line client. The
kill
command along with thetopologyidentifier
stops the topology entirely. It can be paused and restarted without fully
stopping using
deactivate
and
activate,
respectively. You can also
pause and restart the topology from the Storm web interface by selecting the
topology in the UI.
Starting a Topology Project
The easiest way to get started developing a topology project is to use Maven
to include all of the requisite dependencies. The following is a minimal
pom.xml
file needed to start a Java-based Storm topology. It includes the
minimal dependencies, including the link to the
clojars.org
repository
where Storm's maven packages are hosted. It also includes the
shade
plug-in, which is used to build so-called “fat jars” that add other
dependencies not included with Storm itself:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
