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
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Dynamic log level settings


The dynamic log level allows us to change the log level setting of the topology on the runtime from the Storm CLI and the Storm UI.

Updating the log level from the Storm UI

Go through the following steps to update the log level from the Storm UI:

  1. Deploy SampleStormClusterTopology again on the Storm cluster if it is not running.
  2. Browse the Storm UI at http://nimbus-node:8080/.
  3. Click on the storm_example topology.

 

  1. Now click on the Change Log Level button to change the ROOT logger of the topology, as shown in the following are the screenshots:
  1. Configure the entries mentioned in the following screenshots change the ROOT logger to ERROR:
  1. If you are planning to change the logging level to DEBUG, then you must specify the timeout (expiry time) for that log level, as shown in the following screenshots:
  1. Once the time mentioned in the expiry time is reached, the log level will go back to the default value:
  1. Clear button mentioned in the Action column will clear the log setting, and...