What would be the procedure in this case? Run drain on the node that is
disagreeing? But is it enough to run just drain or you suggest drain + rm
system files?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Two-versions-of-schema
rg
Betreff: Re: AW: Two versions of schema
In my case all hosts were reachable and I ran nodetool ring before running
the schema update. I don't think it was because of node being down. I tihnk
for some reason it just took over 10 secs because I was reducing key_cache
from 1M to 1000. I th
hence 10
sec default may not be the right way.
What is drain?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Two-versions-of-schema-tp6277365p6284276.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
> Schema changes should not be seen as something that can be done regularly. It
> should not be done programmatically. There should always be some operator
> looking at the cluster verifying that all nodes are reachable and ring is ok.
> And then issue schema changes one at a time using the cli.
.com]
Gesendet: Freitag, 15. April 2011 21:04
An: cassandra-u...@incubator.apache.org
Betreff: Two versions of schema
Is there a problem?
[default@StressKeyspace] update column family StressStandard with
keys_cached=100;
854ee0a0-6792-11e0-81f9-93d987913479
Waiting for schema agreement...
The
I don't think I got correct answer to my original post. Can someone please
help?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Two-versions-of-schema-tp6277365p6280070.html
Sent from the cassandra-u...@incubator.apache.org mailing list ar
what it means and it's
implications?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Two-versions-of-schema-tp6277365p6277365.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
