Re: incomplete schema sync for new node

Oops, forgot to mention that we're using Cassandra 0.7.2. On 07/01/2011 05:46 PM, Jeremy Stribling wrote: Hi all, I'm running into a problem with Cassandra, where a new node coming up seems to only get an incomplete set of schema mutations when bootstrapping, and as a resu

incomplete schema sync for new node

Hi all, I'm running into a problem with Cassandra, where a new node coming up seems to only get an incomplete set of schema mutations when bootstrapping, and as a result hits an "IllegalStateException: replication factor (3) exceeds number of endpoints (2)" error. I will describe the sequenc

Re: Attempt to assign id to existing column family.

On 03/30/2011 02:54 PM, Jeremy Stribling wrote: After restarting a Cassandra 0.7.2 node, the node catches an exception during initialization and refuses to start: Caused by: org.apache.cassandra.config.ConfigurationException: Attempt to assign id to existing column family. at

Attempt to assign id to existing column family.

After restarting a Cassandra 0.7.2 node, the node catches an exception during initialization and refuses to start: Caused by: org.apache.cassandra.config.ConfigurationException: Attempt to assign id to existing column family. at org.apache.cassandra.config.CFMetaData.map(CFMetaData.jav

Re: changing the replication level on the fly

On 01/18/2011 11:36 AM, Edward Capriolo wrote: On Tue, Jan 18, 2011 at 2:14 PM, Jeremy Stribling wrote: Hi, I've noticed in the new Cassandra 0.7.0 release that if I have a keyspace with a replication level of 2, but only one Cassandra node, I cannot insert anything into the s

changing the replication level on the fly

Hi, I've noticed in the new Cassandra 0.7.0 release that if I have a keyspace with a replication level of 2, but only one Cassandra node, I cannot insert anything into the system. Likely this was a bug in the old release I was using (0.6.8 -- is there a JIRA describing this problem?). Howev