Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Real-time Analytics with Storm and Cassandra

You're reading from  Real-time Analytics with Storm and Cassandra

Product type Book
Published in Mar 2015
Publisher
ISBN-13 9781784395490
Pages 220 pages
Edition 1st Edition
Languages
Author (1):
Shilpi Saxena Shilpi Saxena
Profile icon Shilpi Saxena
Toc

Table of Contents (19) Chapters close

Real-time Analytics with Storm and Cassandra
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Let's Understand Storm 2. Getting Started with Your First Topology 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 Quiz Answers Index

Cassandra cluster scaling – adding a new node


Cassandra scales very easily, and with zero downtime. This is one of the reasons why it is chosen over many other contenders. The steps are pretty straightforward and simple:

  1. You need to set up Cassandra on the nodes to be added. Don't start the Cassandra process yet; first, follow these steps:

    1. Update the seed nodes in Cassandra.yaml under seed_provider.

    2. Make sure the tmp folders are clean.

    3. Add auto_bootstrap to Cassandra.yaml and set it to true.

    4. Update cluster_name in Cassandra.yaml.

    5. Update listen_address/broadcast_address in Cassandra.yaml.

  2. Start all the new nodes one by one, pausing for at least 5 minutes between two consecutive starts.

  3. Once the node is started, it will proclaim its share of data based on the token range it owns and start streaming that in. This could be verified using the nodetoolnetstat command, as shown in the following code:

    mydomain@my-cass1:/home/ubuntu$ /usr/local/cassandra/apache- cassandra-1.1.6/bin/nodetool -h 10.3.12.29...
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 €14.99/month. Cancel anytime}