How to understand the local directory structure of Storm

This article is to share with you about how to understand the local directory structure of Storm. The editor thinks it is very practical, so I share it with you. I hope you can get something after reading this article.

Background: make sure you have successfully installed Storm and found the local folder of storm-local

Purpose: what is the local folder in Storm? The information held on zookeeper is well known, so

Do you have local information?

/ {storm-local-dir} | |-/ nimbus |-/ inbox-- the jar package uploaded from the nimbus client | it will be in this directory | |-/ stormjar- {uuid} .jar-- where {uuid} indicates that the uploaded jar package | A generated uuid |-/ stormdist |-/ {topology-id} |-/ stormjar.jar-contains all the codes of this topology | | jar package (from nimbus/inbox | | face moved) | ) |-/ stormcode.ser-- the serialization of this topology object |-/ stormconf.ser-- the configuration for running this topology | |-/ supervisor |-/ stormdist |-/ {topology-id} |-/ resources | -- what is saved here is topology's | resources directory in the jar package | all the following files |-/ stormjar.jar-- downloaded from the nimbus machine | topology's jar package | |-/ stormcode.ser-- downloaded from the nimbus machine | the sequence of this topology object | converted form |-/ stormconf.ser-- downloaded from the nimbus machine | The configuration to run this topology |-/ localstate-- the localstate of supervisor |-/ tmp-- temporary directory Go up and down from Nimbus | | the files loaded will be stored in this directory first | | in the record | Then do some simple | | process and then copy to | | stormdist/ {topology-id} | | go inside | |-/ {uuid} |-/ stormjar.jar-- download from above Nimbus | | incoming work jar package | |-/ workers | |-/ {worker-id} | |-/ pids-there may be multiple children in a worker | | process may have multiple pid | |-/ {pid}-- the pid of the JVM running this worker | |-/ heartbeats-- the heartbeat information of the | worker on this supervisor machine | |-/ {worker-id}-- there is a worker stored in it | Heartbeat: mainly includes id of heartbeat and worker

The above is how to understand the local directory structure of Storm. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.