I’ll take a slightly different position - people who never expect to change the
cluster shouldn’t care which they’re using, people who want to grow by 10-20%
often should probably use vnodes, everyone else can probably figure out how to
get by with single token, with the caveat that they’ll prob
I think cost is a very important point if you are going to use *single**
token i*f your cluster will be very large , because every time the cluster
is expanded, the nodes need to be doubled.100 -> 200, 200->400 ...
This is one of the reasons why we maintain many small clusters.
of course its avail
Hi Community,
We are currently using Cassandra version 4.1.3 and have encountered an
issue related to tombstone generation. We have two tables storing monthly
data: table_september and table_october. Each table has a TTL of 30 days.
For the month of October, data is being inserted into the table_
You don’t have to double. You can add 1 node at a time - you just have to move every other token to stay balancedMost people don’t write the tooling to do that, but it’s not that complicatedCalculate the token positions with N nodesCalculate the token positions with N+1 nodes Bootstrap the new mach
Are you using collections?
—
Jon Haddad
Rustyrazorblade Consulting
rustyrazorblade.com
On Tue, Oct 8, 2024 at 10:52 PM Naman kaushik
wrote:
> Hi Community,
>
> We are currently using Cassandra version 4.1.3 and have encountered an
> issue related to tombstone generation. We have two tables sto
Hi Long,
This is the best resource on understanding tokens per node and their impact
on operations / availability:
https://jolynch.github.io/pdf/cassandra-availability-virtual.pdf
I am one of those users that used a single token. It does make certain
operations simpler but it comes with a cost: c
Here’s the best post I’m aware of:
https://jolynch.github.io/pdf/cassandra-availability-virtual.pdf
> On Oct 7, 2024, at 17:30, Long Pan wrote:
>
>
> Hi Cassandra Community,
>
> I’m currently exploring the use of single vnode (single token) per node in
> large-scale Cassandra deployments. I
