count me in on being interested in what DataStax is calling “Big Node.”
Would love to be able to use denser nodes, if the headaches are reduced.
Sean Durity
From: Ben Slater
Sent: Wednesday, November 07, 2018 6:08 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Multiple cluster for a
Thank you all, Actually, "the documents" i mentioned in my question, was a talk
in youtube seen long time ago and could not find it. Also noticing that a lot
of companies like Netflix built hundreds of Clusters each having 10s of nodes
and saying that its much stable, i just concluded that big c
I tend to recommend an approach similar to Eric’s functional sharding
although I describe it at quality of service sharding - group your small,
hot data into one cluster and your large, cooler data into another so you
can provision infrastructure and tune according. I guess it depends on you
manage
Interesting approach Eric, thanks for sharing that.
Regarding this:
> I've read documents recommended to use clusters with less than 50 or 100
nodes (Netflix got hundreds of clusters with less 100 nodes on each).
Not sure where you read that, but it's nonsense. We work with quite a few
clusters
We are engaging in both strategies at the same time:
1) We call it functional sharding - we write to clusters targeted according
to the type of data being written. Because different data types often have
different workloads this has the nice side effect of being able to tune
each cluster accordin
Hi, One of my applications requires to create a cluster with more than 100
nodes, I've read documents recommended to use clusters with less than 50 or 100
nodes (Netflix got hundreds of clusters with less 100 nodes on each). Is it a
good idea to use multiple clusters for a single application, ju
