Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Cassandra High Availability

You're reading from   Cassandra High Availability Harness the power of Apache Cassandra to build scalable, fault-tolerant, and readily available applications

Arrow left icon
Product type Paperback
Published in Dec 2014
Publisher Packt
ISBN-13 9781783989126
Length 186 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
 Strickland Strickland
Author Profile Icon Strickland
Strickland
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Cassandra High Availability
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Cassandra's Approach to High Availability FREE CHAPTER 2. Data Distribution 3. Replication 4. Data Centers 5. Scaling Out 6. High Availability Features in the Native Java Client 7. Modeling for High Availability 8. Antipatterns 9. Failing Gracefully Index

Snitch changes


As you will recall from Chapter 4, Data Centers, the snitch tells Cassandra what your network topology looks like, and therefore affects data placement in the cluster. If you haven't inserted any data, or if the change doesn't alter your topology, you can change the snitch without consequence. Otherwise, multiple steps are required as well as a full cluster restart, which will result in downtime.

How do you know if your topology has changed? If you're not adding or removing nodes while changing the snitch, your topology has not changed. Presuming no change, the following procedure should be used to change snitches:

  1. Update your topology properties files, which means cassandra-topology.properties or cassandra-rackdc.properties, depending on which snitch you specify. In the case of the PropertyFileSnitch, make sure all nodes have the same file. For GossipingPropertyFileSnitch or EC2MultiRegionSnitch, each node should have a file indicating its place in the topology.

  2. Update the snitch...

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 $15.99/month. Cancel anytime
Visually different images