Re: Schema Changes

Schema are propagated by GOSSIP you can check schema propagation cluster wide with nodetool describecluster or "nodetool gossipinfo | grep SCHEMA | cut -f3 -d: | sort | uniq -c" You'd better send your DDL instruction to only one node (for example by using the whitelist load balancing policy with

Re: Schema Changes

We used cassandra migration tool for schema versioning and schema agreement. Check it out here . Short: When executing schema altering statements use these to wait for schema propagation resultSet.getExecutionInfo().isSchemaInAgreemen

Re: Schema Changes

You can start here: https://issues.apache.org/jira/browse/CASSANDRA-10699 And here: http://stackoverflow.com/questions/20293897/cassandra-resolution-of-concurrent-schema-changes In a nutshell, schema changes works best when issued serially, when all nodes are up, and reachable. When these 3 con

Re: Schema changes: where in Java code are they sent?

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

Re: Schema changes: where in Java code are they sent?

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

Re: Schema changes: where in Java code are they sent?

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

Re: Schema changes: where in Java code are they sent?

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? >

Re: Schema changes not getting picked up from different process

What clients are the scripts using ? This sounds like something that should be handled in the client. I would worry about holding a long running connection to a single node. There are several situations where the correct behaviour for a client is to kill a connection and connect to another nod

Re: Schema changes not getting picked up from different process

Hi Dave, Thank you for your answer. 2012/5/25 Dave Brosius > What version are you using? > I am using version 1.1.0 > It might be related to > https://issues.apache.org/jira/browse/CASSANDRA-4052 > Indeed the Issue you suggested goes into the direction of my problem. However, things are a

Re: Schema changes not getting picked up from different process

What version are you using? It might be related to https://issues.apache.org/jira/browse/CASSANDRA-4052 On 05/25/2012 07:32 AM, Victor Blaga wrote: Hi all, This is my first message on this posting list so I'm sorry if I am breaking any rules. I just wanted to report some sort of a problem th