I would recommend against 2.0.12 as long as nodetool cleanup is broken and wait for 2.0.13.
On Tue, Mar 3, 2015 at 11:43 AM, Nate McCall <n...@thelastpickle.com> wrote: > Did you run 'upgrade sstables'? See these two sections in 2.0's NEWS.txt: > https://github.com/apache/cassandra/blob/cassandra-2.0/NEWS.txt#L132-L141 > https://github.com/apache/cassandra/blob/cassandra-2.0/NEWS.txt#L195-L198 > > It's a good idea to move up to 2.0.12 while your at it. There have been a > number of bugfixes. > > On Tue, Mar 3, 2015 at 12:37 PM, Fabrice Facorat < > fabrice.faco...@gmail.com> wrote: > >> Hi, >> >> we have a 52 Cassandra nodes cluster running Apache Cassandra 1.2.13. >> As we are planning to migrate to Cassandra 2.0.10, we decide to do >> some tests and we noticed that once a node in the cluster have been >> upgraded to Cassandra 2.0.x, restarting a Cassandra 1.2.x will fail. >> >> The tests were done on a 6 nodes cluster running Apache Cassandra >> 1.2.13 (x5) + Apache Cassandra 2.0.10 (x1) and using java 1.7.0_07. >> The cassandra 1.2.x is failing with the following error in output.log : >> >> INFO 15:18:41,233 Initializing system_traces.events >> org.apache.cassandra.db.marshal.MarshalException: unable to coerce >> 'credval' to a formatted date (long) >> at >> org.apache.cassandra.db.marshal.DateType.dateStringToTimestamp(DateType.java:115) >> at >> org.apache.cassandra.db.marshal.DateType.fromString(DateType.java:83) >> at >> org.apache.cassandra.db.marshal.ReversedType.fromString(ReversedType.java:82) >> at >> org.apache.cassandra.config.ColumnDefinition.fromSchema(ColumnDefinition.java:231) >> at >> org.apache.cassandra.config.CFMetaData.addColumnDefinitionSchema(CFMetaData.java:1524) >> at >> org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1456) >> at >> org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:306) >> at >> org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:287) >> at >> org.apache.cassandra.db.DefsTable.loadFromTable(DefsTable.java:154) >> at >> org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:583) >> at >> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:253) >> at >> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:381) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:601) >> at >> org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:212) >> Caused by: java.text.ParseException: Unable to parse the date: credval >> at >> org.apache.commons.lang.time.DateUtils.parseDateWithLeniency(DateUtils.java:359) >> at >> org.apache.commons.lang.time.DateUtils.parseDateStrictly(DateUtils.java:305) >> at >> org.apache.cassandra.db.marshal.DateType.dateStringToTimestamp(DateType.java:111) >> ... 16 more >> Cannot load daemon >> Service exit with a return value of 3 >> >> We did some tests with a very simple schema without ReversedType, but >> they failed too. >> >> We did look at CASSANDRA-6695 and CASSANDRA-8462, and we had applied >> the corresponding patch, but without success. >> >> Does someone know a way to avoid this issue ? >> >> >> -- >> Close the World, Open the Net >> http://www.linux-wizard.net >> > > > > -- > ----------------- > Nate McCall > Austin, TX > @zznate > > Co-Founder & Sr. Technical Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com >
