Then there is nothing to repair.
Set a better token, cassandra-cli to increase the RF to 2 and then kick off
repair.
A
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 26/09/2011, at 10:12 AM, Radim Kolar wrote:
> Dne 25.9.2011 22:4
Dne 25.9.2011 22:40, aaron morton napsal(a):
That message will be logged if there RF on the keyspace is 1 or if the other
nodes are not up.
What's the RF ?
rf is 1.
That message will be logged if there RF on the keyspace is 1 or if the other
nodes are not up.
What's the RF ?
You should also sort out the tokens before going to far.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 25/09/201
If you join a node with auto_bootstrap=false you had better be working
at quorum or higher to avoid stale/not found reads. You should then
repair the node right away to get all the missing data back on the
node. This is not suggested. It is best to leave auto_boostrap=true
and let Cassandra h
2011/9/13 Radim Kolar
> If i add node without bootstrap and run repair on both nodes then no data
> are moved to new node, just new writes are going to new node. This is
> expected behaviour or it is some kind of user or program error?
>
No. This is exactly what you are asking the node to do by
If i add node without bootstrap and run repair on both nodes then no
data are moved to new node, just new writes are going to new node. This
is expected behaviour or it is some kind of user or program error?
