Book Image

Mastering Apache Storm

By : Ankit Jain
Book Image

Mastering Apache Storm

By: Ankit Jain

Overview of this book

Apache Storm is a real-time Big Data processing framework that processes large amounts of data reliably, guaranteeing that every message will be processed. Storm allows you to scale your data as it grows, making it an excellent platform to solve your big data problems. This extensive guide will help you understand right from the basics to the advanced topics of Storm. The book begins with a detailed introduction to real-time processing and where Storm fits in to solve these problems. You’ll get an understanding of deploying Storm on clusters by writing a basic Storm Hello World example. Next we’ll introduce you to Trident and you’ll get a clear understanding of how you can develop and deploy a trident topology. We cover topics such as monitoring, Storm Parallelism, scheduler and log processing, in a very easy to understand manner. You will also learn how to integrate Storm with other well-known Big Data technologies such as HBase, Redis, Kafka, and Hadoop to realize the full potential of Storm. With real-world examples and clear explanations, this book will ensure you will have a thorough mastery of Apache Storm. You will be able to use this knowledge to develop efficient, distributed real-time applications to cater to your business needs.
Table of Contents (19 chapters)
Title Page
About the Author
About the Reviewers
Customer Feedback

Isolation scheduler

The isolation scheduler provides a mechanism for the easy and safe sharing of Storm cluster resources among many topologies. The isolation scheduler helps to allocate/reserve the dedicated sets of Storm nodes for topologies within the Storm cluster.

We need to define the following property in the Nimbus configuration file to switch to the isolation scheduler:

storm.scheduler: org.apache.storm.scheduler.IsolationScheduler 

We can allocate/reserve the resources for any topology by specifying the topology name and the number of nodes inside the isolation.scheduler.machines property, as mentioned in the following section. We need to define the isolation.scheduler.machines property in the Nimbus configuration, as Nimbus is responsible for the distribution of topology workers between Storm nodes:

  "Topology-Test1": 2 
  "Topology-Test2": 1 
  "Topology-Test3": 4 

In the preceding configuration, two nodes are assigned to Topology-Test1, one node is...