5. Scaling Out | Cassandra High Availability

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Cassandra High Availability

By : Strickland

4.6 (14)

Cassandra High Availability

4.6 (14)

By: Strickland

Overview of this book

If you are a developer or DevOps engineer who understands the basics of Cassandra and are ready to take your knowledge to the next level, then this book is for you. An understanding of the essentials of Cassandra is needed.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Cassandra's Approach to High Availability

1. Cassandra's Approach to High Availability

ACID

The monolithic architecture

The master-slave architecture

Cassandra's solution

Cassandra's architecture

Summary

2. Data Distribution

2. Data Distribution

Hash table fundamentals

Consistent hashing

Token assignment

Partitioners

Summary

3. Replication

3. Replication

The replication factor

Snitches

Consistency conflicts

Balancing the replication factor with consistency

Summary

4. Data Centers

4. Data Centers

Use cases for multiple data centers

Data center setup

Replication across data centers

Summary

5. Scaling Out

5. Scaling Out

Choosing the right hardware configuration

Scaling out versus scaling up

Growing your cluster

How to scale out

How to scale up

Removing nodes

Other data migration scenarios

Snitch changes

Summary

6. High Availability Features in the Native Java Client

6. High Availability Features in the Native Java Client

Thrift versus the native protocol

Setting up the environment

Connecting to the cluster

Executing statements

Handling asynchronous requests

Load balancing

Failing over to a remote data center

Tying it all together

Summary

7. Modeling for High Availability

7. Modeling for High Availability

How Cassandra stores data

Understanding compaction

CQL under the hood

Understanding queries

How collections are stored

Working with time-series data

Designing for immutability

Working with geospatial data

Summary

8. Antipatterns

8. Antipatterns

Multikey queries

Secondary indices

Distributed joins

Deleting data

Unbounded row growth

Summary

9. Failing Gracefully

9. Failing Gracefully

Knowledge is power

Logging

Monitoring node metrics

When a node goes down

Backing up data

Summary

Index

Index

Customer Reviews

4.6 (14)

5 star

64.3%

4 star

35.7%

3 star

0

2 star

0

1 star

0

Scaling out versus scaling up

So you know it's time to add more muscle to your cluster, but how do you know whether to scale up or out?

If you're not familiar with the difference, scaling up refers to converting existing infrastructure into better or more robust hardware (or instance types in cloud environments). This can mean adding storage capacity, increasing memory, moving to newer machines with more cores, and so on.

Scaling out simply means adding more machines that roughly match the specifications of the existing machines. Since Cassandra scales linearly with its peer-to-peer architecture, scaling out is often more desirable.

Note

In general, it is better to replace physical hardware components incrementally rather than all at one time. This is because in large systems, failures tend to occur after hardware ages to a certain point, which is statistically likely to happen simultaneously for some subset of your nodes.

For example, purchasing a large amount of drives from a single source...

Search

Your notes and bookmarks