Process events from Azure Event Hubs with Storm on HDInsight (Java)

Última atualização: 05/10/2017
Editar no GitHub

Learn how to use Azure Event Hubs with Storm on HDInsight. This example uses Java-based components to read and write data in Azure Event Hubs. It also demonstrates how to write data to the default storage for your cluster.

Note: This example is created and tested on HDInsight. It may work on other Hadoop distributions, but you will need to change things like the scheme used to store data to HDFS.


How it works

The resources/writer.yaml topology writes random data to an event hub. The data is generated by the DeviceSpout component, and is a random device ID and device value. So it's simulating some hardware that emits a string ID and a numeric value.

The resources/reader.yaml topology reads data from Event Hub (the data written by EventHubWriter,) parses the JSON data. It also emits the deviceId and deviceValue to Storm logs.

The resources/readertofile.yaml topology is the same as the reader.yaml topology, but it also uses the HDFS-bolt component to write data to the HDFS-compatible file system used by HDInsight.

The data format in Event Hub is a JSON document with the following format:

{ "deviceId": "unique identifier", "deviceValue": some value }

The reason it's stored in JSON is compatibility - I ran into someone who wasn't formatting data sent to Event Hub as JSON (from a Java application,) and was reading it into a Java app. Worked fine. Then they wanted to replace the reading component with a C# application that expected JSON. Problem! Always store to a nice format that is future proofed in case your components change.

Required information

  • An Azure event hub with two shared access policies:

    • The writer policy must have write permission to the event hub.
    • The reader policy must have listen permissions to the event hub.
  • To connect to the event hub from Storm, you need the following information:

    • The connection string for the writer policy.
    • The policy key for the reader policy.
    • The name of your Event Hub.
    • The Service Bus namespace that your Event Hub was created in.
    • The number of partitions available with your Event Hub configuration.

    For information on creating an event hub, see the Create Event Hubs document.

Confgure and build

  1. Fork & clone the repository so you have a local copy.

  2. Add the Event Hub configuration to the file. This is used to configure the spout that reads from Event Hub and the bolt that writes to it.

  3. Use mvn package to build everything.

    Once the build completes, the target directory will contain a file named EventHubExample-1.0-SNAPSHOT.jar.

Test locally

Since these topologies just read and write to Event Hubs, you can test them locally if you have a Storm development environment. Use the following steps to run locally in the dev environment:

  1. Run the writer:

    storm jar EventHubExample-1.0-SNAPSHOT.jar org.apache.storm.flux.Flux --local -R /writer.yaml --filter
  2. Run the reader:

    storm jar EventHubExample-1.0-SNAPSHOT.jar org.apache.storm.flux.Flux --remote -R /reader.yaml --filter

Output is logged to the console when running locally. Use Ctrl+C to stop the topology.


  1. Use SCP to copy the jar package to your HDInsight cluster. Replace USERNAME with the SSH user for your cluster. Replace CLUSTERNAME with the name of your HDInsight cluster:

    scp ./target/EventHubExample-1.0-SNAPSHOT.jar
    For more information on using `scp` and `ssh`, see [Use SSH with HDInsight](
  2. Use SCP to copy the file to the server:

  3. Once the file has finished uploading, use SSH to connect to the HDInsight cluster. Replace USERNAME the the name of your SSH login. Replace CLUSTERNAME with your HDInsight cluster name:

  4. Use the following commands to start the topologies:

    storm jar EventHubExample-1.0-SNAPSHOT.jar org.apache.storm.flux.Flux --remote -R /writer.yaml --filter
    storm jar EventHubExample-1.0-SNAPSHOT.jar org.apache.storm.flux.Flux --remote -R /reader.yaml --filter

    This will start the topologies and give them a friendly name of "reader" and "writer".

  5. To view the logged data, go to, where CLUSTERNAME is the name of your HDInsight cluster. Select the topologies and drill down to the components. Select the port entry for an instance of a component to view logged information.

  6. Use the following commands to stop the reader:

    storm kill eventhubreader

Write output to HDFS

By default, the components needed to write to WASB or ADL (the file schemes used by HDInsight's HDFS-compatable storage) are not in Storm's classpath. To add them and write output to file, use the following steps:

  1. From the Azure Portal, select your HDInsight cluster.

  2. Select the Script actions entry, and then select + Submit new.

  3. Use the following values to fill in the Submit script action form:

    • Select a script: Select Custom
    • Name: Enter a name for this script. This is how it will appear in the script history.
    • Bash script URI:
    • Node type(s): Select Nimbus and Supervisor node types.
    • Parameters: Leave this field blank.
    • Persist: Check this field.
  4. Select Create to run the script action.

  5. Once the script completes, use the following command to start the topology that writes data to file:

    storm jar EventHubExample-1.0-SNAPSHOT.jar org.apache.storm.flux.Flux --remote -R /readtofile.yaml --filter
  6. To view the files generated by the topology, use the following command:

    hdfs dfs -ls /stormdata

    This command returns results similar to the following:

    Found 4 items
    -rw-r--r--   1 storm supergroup    1048619 2017-10-05 17:25 /stormdata/hdfs-bolt-5-0-1507224331637.txt
    -rw-r--r--   1 storm supergroup    1048608 2017-10-05 17:25 /stormdata/hdfs-bolt-5-1-1507224340630.txt
    -rw-r--r--   1 storm supergroup    1048621 2017-10-05 17:25 /stormdata/hdfs-bolt-5-2-1507224342046.txt

    To view the contents of a file, use the following command:

    hdfs dfs -text /stormdata/filename

    Replace filename with the name of one of the files.

  7. To stop the topologies, use the following commands:

    storm kill eventhubwriter
    storm kill eventhubreader

Project code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.