Good morning,
Sorry for the slow reply here. I finally had some time to test cqlsh tracing on
a ccm cluster with 2 of 3 nodes down, to see if the unavailable error was due
to cqlsh or my query. Reply inline below.
On 15/01/2015 12:46, "Tyler Hobbs"
mailto:ty...@datastax.com>> wrote:
On Thu, J
On Thu, Jan 15, 2015 at 6:30 AM, Richard Dawe
wrote:
>
> I thought it might be quorum consistency level, because of the because I
> was seeing with cqlsh. I was testing with ccm with C* 2.0.8, 3 nodes,
> vnodes enabled ("ccm create test -v 2.0.8 -n 3 --vnodes -s”). With all
> three nodes up, my
Hi Tyler,
Thank you for your quick reply; follow-up inline below.
On 14/01/2015 19:36, "Tyler Hobbs"
mailto:ty...@datastax.com>> wrote:
On Wed, Jan 14, 2015 at 5:13 PM, Richard Dawe
mailto:rich.d...@messagesystems.com>> wrote:
I’ve been trying to find the Java code where the schema migration
On Wed, Jan 14, 2015 at 5:13 PM, Richard Dawe
wrote:
>
> I’ve been trying to find the Java code where the schema migration is
> sent to the other nodes in the cluster, to understand what the requirements
> are for successfully applying the update. E.g.: is QUORUM consistency level
> applied?
>
Hello,
I’m doing some research on schema migrations for Cassandra.
I’ve been playing with cqlsh with TRACING ON, and I can see that a schema
change like “CREATE TABLE” is sent to all nodes in the cluster. And also that
“CREATE TABLE” fails if only one of my three nodes is up (with replication
