The advice Tyler gave is the correct. Do a rolling upgrade, and shapshot if you want to have a rollback.
My personal approach is to upgrade a node or two and let run for a few hours. Just to avoid the situation where you uprade every node and then discover some problem that causes wailing and gnashing of teeth. In general, node by node: * drain * snapshot * shutdown * upgrade * turn on. When they are all up I snap shot again if there is space. Then run upgradetables. Cheers ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 13/07/2012, at 11:06 AM, Roshan wrote: > Thanks Aaron. My major concern is upgrade node by node. Because currently we > are using 1.0.6 in production and plan is to upgrade singe node to 1.1.2 at > a time. > > Any comments? > > Thanks. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Concerns-about-Cassandra-upgrade-from-1-0-6-to-1-1-X-tp7581197p7581221.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com.
