Thanks for your help Peter.
We gave up and rolled back to our mysql implementation (we did all writes to
our old store in parallel so we did not lose anything).
Problem was that every solution we came up with would require at least on major
compaction before the new nodes could join and our clus
> Currently I am copying all data files (thats all existing data) from one node
> to the new nodes in hope that I could than manually assign them their new
> tokenrange (nodetool move) and do cleanup.
Unless I'm misunderstanding you I believe you should be setting the
initial token. nodetool mov
Hi good people.
I underestimated load during peak times and now I'm stuck with our production
cluster.
Right now its 3 nodes, rf 3 so everything is everywhere. We have ~300GB data
load. ~10MB/sec incoming traffic and ~50 (peak) reads/sec to the cluster
The problem derives from our quorum read
