Yeah it happens from time to time even if everything seems to be fine that
schema changes don't work correctly. But it's always repairable with the
described procedure. Therefore the operator being available is a must have I
think.
Drain is a nodetool command. The node flushes data and stops accepting new
writes. This just speeds up bringing the node back up again in this case.
Probably a flush is equally acceptable.
-Ursprüngliche Nachricht-
Von: mcasandra [mailto:mohitanch...@gmail.com]
Gesendet: Montag, 18. April 2011 18:27
An: cassandra-u...@incubator.apache.org
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 think it might be taking long to trim the keys 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.
