AW: AW: Two versions of schema
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.
Re: AW: AW: Two versions of schema
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-tp6277365p6287863.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
Re: Two versions of schema
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. +1. I think this is a great take-away w.r.t. schema changes. -- / Peter Schuller
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.
Re: Two versions of schema
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 archive at Nabble.com.
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 schema has not settled in 10 seconds; further migrations are ill-advised until it does. Versions are 854ee0a0-6792-11e0-81f9-93d987913479:[10.18.62.202, 10.18.62.203, 10.18.62.200, 10.18.62.204, 10.18.62.199, 10.18.62.196, 10.18.62.197],22d165ff-6783-11e0-81f9-93d987913479:[10.18.62.198] I remember reading somewhere before that when you have 2 versions of schemas you are basically in trouble. Can someone explain 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.
