Gossip related stuff eventually becomes the issue
For example, when a new host joins the cluster (or replaces a failed host), the
new bootstrapping tokens go into a “pending range” set. Writes then merge
pending ranges with final ranges, and the data structures involved here weren’t
necessarily
Thank you John and Jeff, I was leaning towards sharding and this really helps
support that opinion. Would you mind explaining a bit more what about vnodes
caused those issues?
From: user@cassandra.apache.org At: 07/10/20 19:06:27To:
user@cassandra.apache.org
Cc: Isaac Reath (BLOOMBERG/ 919 3R
