Thanks Aaron for the reply. I will need to upgrade 1.0.X to 1.1.X first.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Upgrade-from-1-0-11-to-1-2-X-tp7587786p7587825.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive a
Thanks for your short answer. It explains lot.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Upgrade-from-1-0-11-to-1-2-X-tp7587786p7587824.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Also *always* read the NEWS.TXT file with the release.
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 15/05/2013, at 2:57 AM, Edward Capriolo wrote:
> Your not supposed to skip minor versions on upgrade.
> 1.0 -
Your not supposed to skip minor versions on upgrade.
1.0 -> 1.2 = bad
1.0 -> 1.1 -> 1.2 = good
On Tue, May 14, 2013 at 3:07 AM, Roshan wrote:
> While upgrading from 1.0.11 to 1.2.4, I saw this exception in my log.
>
> 2013-05-14 10:50:10,291 ERROR [CassandraDaemon] Exception in thread
> Thread
While upgrading from 1.0.11 to 1.2.4, I saw this exception in my log.
2013-05-14 10:50:10,291 ERROR [CassandraDaemon] Exception in thread
Thread[MutationStage:17,5,main]
java.lang.RuntimeException: java.lang.NullPointerException
at
org.apache.cassandra.service.StorageProxy$HintRunnable.run
