Home » Software Development » One (Token) Ring to Rule Them All

About Luke Tillman

Luke Tillman
Luke is a Technical Evangelist for Apache Cassandra at DataStax. He's spent most of the last 15 years writing code for web applications built on relational databases both large and small. Most recently, before living the glamorous life of an Evangelist at DataStax, he worked as a software engineer at Hobsons on systems used by hundreds of colleges and universities across the U.S. and the World.

One (Token) Ring to Rule Them All

For newcomers to Cassandra, all the terminology can be a little overwhelming at first. If you have experience with relational databases, some concepts like a “Row” or a “Primary Key” will be familiar. But other terms that seem straightforward can often be a little confusing, especially when paired with some of the visuals you see when learning about Cassandra.

For example, take a look at this screenshot from the DataStax OpsCenter management tool:


Now answer these questions:

  • How many token rings are there?
  • How many clusters are there?
  • How many datacenters are there?

How about this slide that I use when introducing new users to Cassandra:


In case you’re wondering, yes, your data actually is “coming to America” in that diagram (pun fully intended). Now answer those same questions:

  • How many token rings are there?
  • How many clusters are there?
  • How many datacenters are there?

Did you answer two for all the questions in both pictures? If you did, you wouldn’t be alone, but you also wouldn’t be correct either. This is one example where the terminology can get a little confusing. Let’s walk through those terms, starting with the last one and working our way backwards.


This is the term that most people are familiar with before starting with Cassandra and if you answered two to the question above then you’re not only correct, but well on your way to understanding this concept. In the computing world, we tend to think of a datacenter as a physical place where our computers reside. The same can be true for a datacenter in Cassandra, but it doesn’t necessarily have to be true.

In Cassandra, a datacenter is just a logical grouping of nodes. This grouping could be based on the physical location of your nodes. For example, we might have a ‘us-east’ and a ‘us-west’ datacenter. But it could also be based on something other than physical location. For example, we might set up a ‘transactional’ and an ‘analytics’ datacenter to run different types of workloads, but the nodes for those datacenters might be physically in the same location.

So how does Cassandra know which nodes belong to which datacenter? Well that’s a little outside the scope of this post, but the short answer is a component in Cassandra called a Snitch. If you want to dig in more, there’s a great explanation of the Snitch on DataStax Academy.

Most of the time when we’re looking at visual depictions of Cassandra like in OpsCenter or my slide above, the nodes are being shown grouped by data center.


If you answered two for this question, I don’t blame you. After all in English, cluster is defined as “a group of things or people that are close together” and in both of those pictures, it sure looks like there are two separate groups of nodes that are close together. But as we just established, most of the time when we see pictures like those we’re seeing nodes grouped by datacenter.

In Cassandra a cluster refers to all the nodes across all the datacenters that are peers (i.e. aware of each other). For both of those images, we’ve got two datacenters where replication is happening between the two of them. So while there are two datacenters, there’s only one cluster depicted in both of those images.

Token Rings

That leaves us with the question about the number of token rings. I tried to be specific by asking about token rings instead of just rings. Oftentimes in Cassandra, the term “ring” (by itself) is used interchangeably with “cluster” to refer to all the nodes across all the datacenters. But when we say token ring we’re usually referring to a specific concept in Cassandra–data distribution.

If you’ve been working with Cassandra then you know by now that when you create a table, you choose a Primary Key. Part of that Primary Key (usually the first column or sometimes the first group of columns) is called the Partition Key. For example, take a look at the users table from KillrVideo:

  userid uuid,
  firstname text,
  lastname text,
  email text,
  created_date timestamp,
  PRIMARY KEY (userid)

Here, the partition key is the userid column. When we insert data into that table, the value for userid is used to determine which nodes in Cassandra will actually store the data. Choosing a Primary Key is important (as a recent blog post highlighted) but what does this have to do with token rings?

Well when Cassandra wants to know where to place data, it takes your Partition Key value and runs it through a consistent hashing function. The hash that comes out of this consistent hashing function is sometimes referred to as a token. And in Cassandra, nodes in your cluster own ranges (or buckets) of all the possible tokens.

So for example, let’s pretend we have a hashing function that outputs tokens from 0-99. The distribution of those tokens across all the nodes in an eight node cluster might look something like this:


Now this is a really simplified example because of the small range of tokens available. In real Cassandra deployments, most people stick with the default Murmur3 partitioner which outputs tokens in the range of -263 to 263 – 1, but even with the larger range available, the principle is the same.

The total range of available tokens and their distribution around the cluster is often referred to as the token ring in Cassandra. And that range of tokens is distributed around the cluster with each node owning a portion of the token ring. So even if we took our 8 node cluster above and logically grouped the nodes across two datacenters, there would still only be one token ring.

This can be really hard to wrap your brain around, especially when you see pictures like the two above. In those pictures, there are definitely two “rings” in the English sense of the word. But in Cassandra terms there’s only one token ring (and only one “ring” if we’re using that term interchangeably with “cluster”), even if the nodes are grouped and displayed as two datacenters.


If you’re struggling with some of the terminology when getting started with Cassandra, hopefully this helps to clear some things up. I highly recommend checking out DS201: Foundations of Apache Cassandra on DataStax Academy for a deeper dive into many of these concepts. Things like replication (and replication strategies) are all built on top of this foundation, so understanding these concepts can go a long way towards becoming a Cassandra guru.

Reference: One (Token) Ring to Rule Them All from our JCG partner Luke Tillman at the Planet Cassandra blog.
(0 rating, 0 votes)
You need to be a registered member to rate this.
1 Comment Views Tweet it!
Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
6. Spring Interview Questions
7. Android UI Design
and many more ....
I agree to the Terms and Privacy Policy

Leave a Reply

1 Comment threads
0 Thread replies
Most reacted comment
Hottest comment thread
1 Comment authors
Tina Pendleton Recent comment authors

This site uses Akismet to reduce spam. Learn how your comment data is processed.

newest oldest most voted
Notify of
Tina Pendleton

I think the token ring is useful for office scenarios and well maintain disciplined places where data to be transmitted in the ring like all devices are connected in the ring topology and only host devices can transmit data to another device because host device has more privileges rather than other devices.