> The queries are rightly designed
Data modeling in Cassandra is 100% gray space; there unfortunately is no right
or wrong design. You'll need to share basic shapes / contours of your data
model for other folks to help you; seemingly innocuous things in a data model
can cause unexpected issues
When it comes to denormalization in Cassandra today your options are to either
do it yourself in your application layer or rely on Materialized Views to do it
for you at the server layer. Neither are production-ready approaches out of the
box (which is one of the biggest flaws in the "provide
Hi folks,
I know it is impossible to run 3.x and 4.x nodes in the same cluster. Is it
possible to run 4.0 and 4.1 nodes together? Is it a good idea?
Doug Whitfield
This e-mail may contain information that is privileged or confidential. If you
are not the intended recipient, please delete the
1. Check for Nagle/delayed-ack, but probably nodelay is getting set by the
driver so it shouldn't be a problem.
2. Check for network latency (just regular old ping among hosts, during
traffic)
3. Check your GC metrics and see if garbage collections line up with
outliers. Some tuning can help
Running mixed versions of Cassandra 3.x and 4.x is supported in the same
cluster for the purpose of live upgrades, though certain features (such as
repair) are not supported while in a mixed-version state.
All of 3.0, 3.x, 4.0, and 4.1 can coexist for the purpose of upgrades. 4.0 and
4.1 are
