Re: [Cas 2.0.2] Looping Repair since activating PasswordAuthenticator

2013-11-04 Thread Dennis Schwan
Hi Yuki, thanks for your answer. I still do nt know if it is expected behaviour that Cassandra tries to repair these 1280 ranges everytime I run a nodetool repair on every node? Regards, Dennis Am 03.11.2013 03:27, schrieb Yuki Morishita: Hi Dennis, As you can see in the output,

Re: [Cas 2.0.2] Looping Repair since activating PasswordAuthenticator

2013-11-02 Thread Yuki Morishita
Hi Dennis, As you can see in the output, [2013-10-31 09:39:59,811] Starting repair command #1, repairing 1280 ranges for keyspace system_auth repair was trying to repair 1280 ranges. I imagine you are using vnodes, and since Cassandra does repair range by range in almost sequentially, it

[Cas 2.0.2] Looping Repair since activating PasswordAuthenticator

2013-10-31 Thread Dennis Schwan
Hi there, I have used this manual: http://www.datastax.com/documentation/cassandra/2.0/webhelp/index.html#cassandra/security/security_config_native_authenticate_t.html to use the PasswordAuthenticator but now everytime I run a nodetool repair it repairs the system_auth keyspace which needs