On Wed, Jul 18, 2012 at 10:27 AM, Douglas Muth doug.m...@gmail.com wrote:
Even though keyspace test1 had a replication_factor of 1 to start
with, each of the above UPDATE KEYSPACE commands caused a new UUID to
be generated for the schema, which I assume is normal and expected.
I believe the
Check the logs server to see if any errors are reported. If possible can you
change the logging to DEBUG and run it ?
Note that the UUID did not change,
Sounds fishy.
There is an issue fixed in 1.1.3 similar to this
https://issues.apache.org/jira/browse/CASSANDRA-4432 But I doubt it applies
Hi folks,
I have an interesting problem in Cassandra 1.1.2, a Google Search
wasn't much help, so I thought I'd ask here.
Essentially, I have a problem keyspace in my 2-node cluster that
keeps me from changing the replication factor on a specific keyspace.
It's probably easier to show what I'm
