Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Real-time Analytics with Storm and Cassandra

You're reading from   Learning Real-time Analytics with Storm and Cassandra Solve real-time analytics problems effectively using Storm and Cassandra

Arrow left icon
Product type Paperback
Published in Mar 2015
Publisher
ISBN-13 9781784395490
Length 220 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Shilpi Saxena Shilpi Saxena
Author Profile Icon Shilpi Saxena
Shilpi Saxena
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Let's Understand Storm 2. Getting Started with Your First Topology FREE CHAPTER 3. Understanding Storm Internals by Examples 4. Storm in a Clustered Mode 5. Storm High Availability and Failover 6. Adding NoSQL Persistence to Storm 7. Cassandra Partitioning, High Availability, and Consistency 8. Cassandra Management and Maintenance 9. Storm Management and Maintenance 10. Advance Concepts in Storm 11. Distributed Cache and CEP with Storm A. Quiz Answers Index

Quiz time

Q.1. State whether the following statements are true or false:

  1. Storm nodes can't be added to the cluster with topologies being executed.
  2. A topology can't survive the Storm node failure.
  3. Storm logs are created on each node in the cluster.
  4. The location of the Storm log creation is configurable.

Q.2. Fill in the blanks:

  1. _______________ is the heartbeat tracker of the cluster.
  2. _______________ is the daemon that's mandatory for topology submission and rebalancing.
  3. The ___________ file holds the worker configuration for the topology.

Q.3. Execute the following use cases to see the internals of Storm:

  1. Start nimbus and check nimbus.log to see what a successful startup should look like.
  2. Start the supervisor and check Supervisor.log to see what a successful startup should look like.
  3. Submit the topology, say a simple WordCount topology, and figure out the worker.log file creation.
  4. Update log4j.properties to change the logging level and verify its impact.
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image