I know what happened here. The node encountering exception during startup
is 1.2 while there is another node of 1.2-beta2.
https://issues.apache.org/jira/browse/CASSANDRA-4416 includes metadata for
system keyspace itself in schema_* tables. Hence, when both nodes were up,
1.2-beta2 node streamed th
well, that didn't go away after I remove all the caches. What should I do
now?
On Wed, Oct 10, 2012 at 2:15 PM, Manu Zhang wrote:
> exception encountered during startup: Attempting to load already loaded
> column family system_traces.sessionsjava.lang.RuntimeException: Attempting
> to load alrea
