In this case I would go on with the nodetool refresh, simply because you use
the machines in a more effective way.(copy data from one node to another, each
node cleans/refresh the data itself) if the clustersetup is the same with
nodes/tokens there’s no need to copy all the data to one point an
It sounds to me that the limitation in this setup is the disks.
if it’s in a mirror the cost for write’s is the dubble.
If you have the flatfile and the db on the same disk there will be a lot of io
wait.
There is also a question of diskspace and fragmentation, if the flat file
occupies 1,2TB o
H,
I've upgraded cassandra from 1.2.13 to 2.0.4 on a cluster of 5 nodes. when i
run nodetool -h localhost ring I see this errormessage in the end:
ERROR 10:33:28,324 Unable to initialize MemoryMeter (jamm not specified as
javaagent). This means Cassandra will be unable to measure object sizes
