Re: replication_factor mismatch

2014-11-11 Thread Philip Thompson
This question probably belongs in the python driver's mailing list. However, if your RF is in fact 3, then that failed query is running at CL.ALL, not CL.QUORUM, which you can see because the required_responses is 3. The consistency: 5 is because consistency levels are an enum class, as seen here:

replication_factor mismatch

2014-11-11 Thread Maxime
Hello, I have a curious behaviour occurring. - 7 Nodes custer - RF on the Keyspace is 3 - Latest version of everything (C* and Python Drivers) - All queries are at QUORUM level Some of my larger queries are timing out, which is ok, it can happen. But looking at the log, I see the following: Read