Re: Cassandra 2.2, 3.0, and beyond
We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7?
Re: Cassandra 2.2, 3.0, and beyond
Hi Jonathan Does documentation fit into the new monthly releases and definition of done as well, or is that part of another process? I didn't see any mention of it in the docs, though I may have missed it. On Thu, 11 Jun 2015 at 9:10 pm Stefan Podkowinski stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- -- Daniel
Re: Cassandra 2.2, 3.0, and beyond
3.1 is EOL as soon as 3.3 (the next bug fix release) comes out. On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Fwd: MarshalException after upgrading to 2.1.6
I've upgraded a node from 2.0.10 to 2.1.6. Before taking down the node, I've run nodetool upgradesstables and nodetool scrub. When starting up the node with 2.1.6, I'm getting a MarshalException (stacktrace included below). For some reason, it seems that C* is trying to convert a text value from the column 'currencyCode' to a UUID, which it isn't. I've had similar errors for two other columns as well, which I could work around by dropping the table, since it wasn't used anymore. The only thing I could do was restoring a snapshot and starting up the old 2.0.10 again. Does anyone have an idea how this can be fixed? Thanks, Tom ERROR 13:51:57 Exception encountered during startup org.apache.cassandra.serializers.MarshalException: unable to make version 1 UUID from 'currencyCode' at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:188) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.marshal.AbstractCompositeType.fromString(AbstractCompositeType.java:242) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.ColumnDefinition.fromSchema(ColumnDefinition.java:397) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.CFMetaData.fromSchemaNoTriggers(CFMetaData.java:1750) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1860) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:321) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:302) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.DefsTables.loadFromKeyspace(DefsTables.java:133) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:696) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:672) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:293) [apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:536) [apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:625) [apache-cassandra-2.1.6.jar:2.1.6] Caused by: org.apache.cassandra.serializers.MarshalException: unable to coerce 'currencyCode' to a formatted date (long) at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:111) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:184) ~[apache-cassandra-2.1.6.jar:2.1.6] ... 12 common frames omitted Caused by: java.text.ParseException: Unable to parse the date: currencyCode at org.apache.commons.lang3.time.DateUtils.parseDateWithLeniency(DateUtils.java:336) ~[commons-lang3-3.1.jar:3.1] at org.apache.commons.lang3.time.DateUtils.parseDateStrictly(DateUtils.java:286) ~[commons-lang3-3.1.jar:3.1] at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:107) ~[apache-cassandra-2.1.6.jar:2.1.6] ... 13 common frames omitted org.apache.cassandra.serializers.MarshalException: unable to make version 1 UUID from 'currencyCode' at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:188) at org.apache.cassandra.db.marshal.AbstractCompositeType.fromString(AbstractCompositeType.java:242) at org.apache.cassandra.config.ColumnDefinition.fromSchema(ColumnDefinition.java:397) at org.apache.cassandra.config.CFMetaData.fromSchemaNoTriggers(CFMetaData.java:1750) at org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1860) at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:321) at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:302) at org.apache.cassandra.db.DefsTables.loadFromKeyspace(DefsTables.java:133) at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:696) at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:672) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:293) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:536) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:625) Caused by: org.apache.cassandra.serializers.MarshalException: unable to coerce 'currencyCode' to a formatted date (long) at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:111) at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:184) ... 12 more Caused by: java.text.ParseException: Unable to parse the date: currencyCode at org.apache.commons.lang3.time.DateUtils.parseDateWithLeniency(DateUtils.java:336) at org.apache.commons.lang3.time.DateUtils.parseDateStrictly(DateUtils.java:286) at
no file cassandra.h found
hey there, I'm trying to compile a script which include the line #include cassandra.h . the compilation is never completed and I have the error file/directory cassandra.h not found. Any idea how to fix this knowing that I have the Datastax Cassandra cpp-driver installed?? In advance, thank you for your response, Sara
Re: Cassandra 2.2, 3.0, and beyond
Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis jbel...@gmail.com: 3.1 is EOL as soon as 3.3 (the next bug fix release) comes out. On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Cassandra 2.2, 3.0, and beyond
As soon as 8099 is done. On Thu, Jun 11, 2015 at 11:53 AM, Pierre Devops pierredev...@gmail.com wrote: Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis jbel...@gmail.com: 3.1 is EOL as soon as 3.3 (the next bug fix release) comes out. On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: no file cassandra.h found
Please send this question to the DataStax C++ mailing list https://groups.google.com/a/lists.datastax.com/forum/#!forum/cpp-driver-user On Thu, Jun 11, 2015 at 8:57 AM, ICHIBA Sara ichi.s...@gmail.com wrote: hey there, I'm trying to compile a script which include the line #include cassandra.h . the compilation is never completed and I have the error file/directory cassandra.h not found. Any idea how to fix this knowing that I have the Datastax Cassandra cpp-driver installed?? In advance, thank you for your response, Sara -- Bests, Alex Popescu | @al3xandru Sen. Product Manager @ DataStax
How the heck do we repair when migrating to 3 replicas on 2.0.x ?
We’re running Cassandra 2.0.9 and just migrated from 2-3 replicas. We changes our consistency level to 2 during this period while we’re running a repair. but we can’t figure out what command to run to repair our data We *think* we have to run “nodetool repair -pr” on each node.. is that right? or do we have to run nodetool -h hostname repair ? We tried to RFTM… we really did :) `” -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile https://plus.google.com/102718274791889610666/posts
Re: Lucene index plugin for Apache Cassandra
Looks awesome, do you have any examples/benchmarks of using these indexes for various cluster sizes e.g. 20 nodes, 60 nodes, 100s+? On 10 June 2015 at 09:08, Andres de la Peña adelap...@stratio.com wrote: Hi all, With the release of Cassandra 2.1.6, Stratio is glad to present its open source Lucene-based implementation of C* secondary indexes https://github.com/Stratio/cassandra-lucene-index as a plugin that can be attached to Apache Cassandra. Before the above changes, Lucene index was distributed inside a fork of Apache Cassandra, with all the difficulties implied. As of now, the fork is discontinued and new users should use the recently created plugin, which maintains all the features of Stratio Cassandra https://github.com/Stratio/stratio-cassandra. Stratio's Lucene index extends Cassandra’s functionality to provide near real-time distributed search engine capabilities such as with ElasticSearch or Solr, including full text search capabilities, free multivariable search, relevance queries and field-based sorting. Each node indexes its own data, so high availability and scalability is guaranteed. We hope this will be useful to the Apache Cassandra community. Regards, -- Andrés de la Peña http://www.stratio.com/ Avenida de Europa, 26. Ática 5. 3ª Planta 28224 Pozuelo de Alarcón, Madrid Tel: +34 91 352 59 42 // *@stratiobd https://twitter.com/StratioBD* -- Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr http://twitter.com/instaclustr | (650) 284 9692
Re: How the heck do we repair when migrating to 3 replicas on 2.0.x ?
On Thu, Jun 11, 2015 at 3:59 PM, Kevin Burton bur...@spinn3r.com wrote: but we can’t figure out what command to run to repair our data We *think* we have to run “nodetool repair -pr” on each node.. is that right? or do we have to run nodetool -h hostname repair ? The simple heuristic is this : If you are repairing a single node, use nodetool repair If you are repairing all nodes, use nodetool -pr You are repairing all nodes, so use nodetool -pr, one node at a time. You may also wish, in this particular case, to do -pr -par (not confusingly named at all!) so that repair is more parallelized. =Rob
RE: Cassandra 2.2, 3.0, and beyond
Considering that 2.1.6 was just released and it is the first “stable” release ready for production in the 2.1 series, won’t it be too soon to EOL 2.1.x when 3.0 comes out in September? Mohammed From: Jonathan Ellis [mailto:jbel...@gmail.com] Sent: Thursday, June 11, 2015 10:14 AM To: user Subject: Re: Cassandra 2.2, 3.0, and beyond As soon as 8099 is done. On Thu, Jun 11, 2015 at 11:53 AM, Pierre Devops pierredev...@gmail.commailto:pierredev...@gmail.com wrote: Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis jbel...@gmail.commailto:jbel...@gmail.com: 3.1 is EOL as soon as 3.3 (the next bug fix release) comes out. On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski stefan.podkowin...@1und1.demailto:stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
RE: Cassandra 2.2, 3.0, and beyond
By that logic, 2.1.0 should have been somewhat as stable as 2.0.10 (the last release of 2.0.x branch before 2.1.0). However, we found out that it took almost 9 months for 2.1.x series to become stable and suitable for production. Going by past history, I am worried that it may take the same time for 2.2 to become stable. Mohammed From: graham sanderson [mailto:gra...@vast.com] Sent: Thursday, June 11, 2015 6:34 PM To: user@cassandra.apache.org Subject: Re: Cassandra 2.2, 3.0, and beyond I think the point is that 2.2 will replace 2.1.x + (i.e. the done/safe bits of 3.0 are included in 2.2).. so 2.2.x and 2.1.x are somewhat synonymous. On Jun 11, 2015, at 8:14 PM, Mohammed Guller moham...@glassbeam.commailto:moham...@glassbeam.com wrote: Considering that 2.1.6 was just released and it is the first “stable” release ready for production in the 2.1 series, won’t it be too soon to EOL 2.1.x when 3.0 comes out in September? Mohammed From: Jonathan Ellis [mailto:jbel...@gmail.com] Sent: Thursday, June 11, 2015 10:14 AM To: user Subject: Re: Cassandra 2.2, 3.0, and beyond As soon as 8099 is done. On Thu, Jun 11, 2015 at 11:53 AM, Pierre Devops pierredev...@gmail.commailto:pierredev...@gmail.com wrote: Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis jbel...@gmail.commailto:jbel...@gmail.com: 3.1 is EOL as soon as 3.3 (the next bug fix release) comes out. On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski stefan.podkowin...@1und1.demailto:stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.comhttp://www.datastax.com/ @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.comhttp://www.datastax.com/ @spyced
Re: Cassandra 2.2, 3.0, and beyond
We've started using the docs-impacting label https://issues.apache.org/jira/issues/?jql=labels%20%3D%20docs-impacting%20AND%20project%20%3D%20CASSANDRA to make it easier for the technical writers to keep up, but otherwise we're not planning any major changes. On Thu, Jun 11, 2015 at 4:50 AM, Daniel Compton daniel.compton.li...@gmail.com wrote: Hi Jonathan Does documentation fit into the new monthly releases and definition of done as well, or is that part of another process? I didn't see any mention of it in the docs, though I may have missed it. On Thu, 11 Jun 2015 at 9:10 pm Stefan Podkowinski stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- -- Daniel -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Question about consistency in cassandra 2.0.9
Hi, I am running a cassandra cluster with 4 dcs. Out of 4 dcs, I have 3 DCs returning right data but 1 dc where I had 1 node down, the data didn't return correct records. So, e.g. DC1 - 386 records (single-token based DC)DC2 - 386 records (vnode based DC)DC3 - 386 records (vnode based DC)DC4 - 178 records (vnode based DC) In DC4 I had one node down due to hardware failures and was getting another spare node bootstrapped. Then why would during bootstrapping process or when 1 node is down in DC4, I would get incorrect records. Thanks Regards,Ken
Re: Question about consistency in cassandra 2.0.9
It looks (I’m guessing with entirely not enough info) that you only have two nodes in DC4, and are probably writing at QUORUM reading at LOCAL_ONE. But please specify your configuration On Jun 11, 2015, at 7:01 PM, K F kf200...@yahoo.com wrote: Hi, I am running a cassandra cluster with 4 dcs. Out of 4 dcs, I have 3 DCs returning right data but 1 dc where I had 1 node down, the data didn't return correct records. So, e.g. DC1 - 386 records (single-token based DC) DC2 - 386 records (vnode based DC) DC3 - 386 records (vnode based DC) DC4 - 178 records (vnode based DC) In DC4 I had one node down due to hardware failures and was getting another spare node bootstrapped. Then why would during bootstrapping process or when 1 node is down in DC4, I would get incorrect records. Thanks Regards, Ken smime.p7s Description: S/MIME cryptographic signature
Re: Cassandra 2.2, 3.0, and beyond
I think the point is that 2.2 will replace 2.1.x + (i.e. the done/safe bits of 3.0 are included in 2.2).. so 2.2.x and 2.1.x are somewhat synonymous. On Jun 11, 2015, at 8:14 PM, Mohammed Guller moham...@glassbeam.com wrote: Considering that 2.1.6 was just released and it is the first “stable” release ready for production in the 2.1 series, won’t it be too soon to EOL 2.1.x when 3.0 comes out in September? Mohammed From: Jonathan Ellis [mailto:jbel...@gmail.com mailto:jbel...@gmail.com] Sent: Thursday, June 11, 2015 10:14 AM To: user Subject: Re: Cassandra 2.2, 3.0, and beyond As soon as 8099 is done. On Thu, Jun 11, 2015 at 11:53 AM, Pierre Devops pierredev...@gmail.com mailto:pierredev...@gmail.com wrote: Hi, 3.x beta release date ? 2015-06-11 16:21 GMT+02:00 Jonathan Ellis jbel...@gmail.com mailto:jbel...@gmail.com: 3.1 is EOL as soon as 3.3 (the next bug fix release) comes out. On Thu, Jun 11, 2015 at 4:10 AM, Stefan Podkowinski stefan.podkowin...@1und1.de mailto:stefan.podkowin...@1und1.de wrote: We are also extending our backwards compatibility policy to cover all 3.x releases: you will be able to upgrade seamlessly from 3.1 to 3.7, for instance, including cross-version repair. What will be the EOL policy for releases after 3.0? Given your example, will 3.1 still see bugfixes at this point when I decide to upgrade to 3.7? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com http://www.datastax.com/ @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com http://www.datastax.com/ @spyced smime.p7s Description: S/MIME cryptographic signature
Re: Question about consistency in cassandra 2.0.9
So, here is the configuration DC 1 - 32 single tokenDC 2 - 32 nodes configured as vnodesDC 3 - 32 nodes configured as vnodesDC 4 - 32 nodes configured as vnodes Write CL just 2 days backs was one and it was changed to LOCAL_QUORUMRead CL has always been ONE I am running on 2.0.9 version of cassandra. Regards,Ken From: graham sanderson gra...@vast.com To: user@cassandra.apache.org; K F kf200...@yahoo.com Sent: Thursday, June 11, 2015 8:14 PM Subject: Re: Question about consistency in cassandra 2.0.9 It looks (I’m guessing with entirely not enough info) that you only have two nodes in DC4, and are probably writing at QUORUM reading at LOCAL_ONE. But please specify your configuration On Jun 11, 2015, at 7:01 PM, K F kf200...@yahoo.com wrote: Hi, I am running a cassandra cluster with 4 dcs. Out of 4 dcs, I have 3 DCs returning right data but 1 dc where I had 1 node down, the data didn't return correct records. So, e.g. DC1 - 386 records (single-token based DC)DC2 - 386 records (vnode based DC)DC3 - 386 records (vnode based DC)DC4 - 178 records (vnode based DC) In DC4 I had one node down due to hardware failures and was getting another spare node bootstrapped. Then why would during bootstrapping process or when 1 node is down in DC4, I would get incorrect records. Thanks Regards,Ken
Re: MarshalException after upgrading to 2.1.6
Can you open a JIRA ticket with details and the schema for that table here? https://issues.apache.org/jira/browse/CASSANDRA On Thu, Jun 11, 2015 at 9:23 AM, Tom van den Berge t...@drillster.com wrote: I've upgraded a node from 2.0.10 to 2.1.6. Before taking down the node, I've run nodetool upgradesstables and nodetool scrub. When starting up the node with 2.1.6, I'm getting a MarshalException (stacktrace included below). For some reason, it seems that C* is trying to convert a text value from the column 'currencyCode' to a UUID, which it isn't. I've had similar errors for two other columns as well, which I could work around by dropping the table, since it wasn't used anymore. The only thing I could do was restoring a snapshot and starting up the old 2.0.10 again. Does anyone have an idea how this can be fixed? Thanks, Tom ERROR 13:51:57 Exception encountered during startup org.apache.cassandra.serializers.MarshalException: unable to make version 1 UUID from 'currencyCode' at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:188) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.marshal.AbstractCompositeType.fromString(AbstractCompositeType.java:242) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.ColumnDefinition.fromSchema(ColumnDefinition.java:397) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.CFMetaData.fromSchemaNoTriggers(CFMetaData.java:1750) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1860) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:321) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:302) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.DefsTables.loadFromKeyspace(DefsTables.java:133) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:696) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:672) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:293) [apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:536) [apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:625) [apache-cassandra-2.1.6.jar:2.1.6] Caused by: org.apache.cassandra.serializers.MarshalException: unable to coerce 'currencyCode' to a formatted date (long) at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:111) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:184) ~[apache-cassandra-2.1.6.jar:2.1.6] ... 12 common frames omitted Caused by: java.text.ParseException: Unable to parse the date: currencyCode at org.apache.commons.lang3.time.DateUtils.parseDateWithLeniency(DateUtils.java:336) ~[commons-lang3-3.1.jar:3.1] at org.apache.commons.lang3.time.DateUtils.parseDateStrictly(DateUtils.java:286) ~[commons-lang3-3.1.jar:3.1] at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:107) ~[apache-cassandra-2.1.6.jar:2.1.6] ... 13 common frames omitted org.apache.cassandra.serializers.MarshalException: unable to make version 1 UUID from 'currencyCode' at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:188) at org.apache.cassandra.db.marshal.AbstractCompositeType.fromString(AbstractCompositeType.java:242) at org.apache.cassandra.config.ColumnDefinition.fromSchema(ColumnDefinition.java:397) at org.apache.cassandra.config.CFMetaData.fromSchemaNoTriggers(CFMetaData.java:1750) at org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1860) at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:321) at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:302) at org.apache.cassandra.db.DefsTables.loadFromKeyspace(DefsTables.java:133) at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:696) at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:672) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:293) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:536) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:625) Caused by: org.apache.cassandra.serializers.MarshalException: unable to coerce 'currencyCode' to a formatted date (long) at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:111) at
Re: MarshalException after upgrading to 2.1.6
Sure! I just opened https://issues.apache.org/jira/browse/CASSANDRA-9582 On Thu, Jun 11, 2015 at 5:27 PM, Tyler Hobbs ty...@datastax.com wrote: Can you open a JIRA ticket with details and the schema for that table here? https://issues.apache.org/jira/browse/CASSANDRA On Thu, Jun 11, 2015 at 9:23 AM, Tom van den Berge t...@drillster.com wrote: I've upgraded a node from 2.0.10 to 2.1.6. Before taking down the node, I've run nodetool upgradesstables and nodetool scrub. When starting up the node with 2.1.6, I'm getting a MarshalException (stacktrace included below). For some reason, it seems that C* is trying to convert a text value from the column 'currencyCode' to a UUID, which it isn't. I've had similar errors for two other columns as well, which I could work around by dropping the table, since it wasn't used anymore. The only thing I could do was restoring a snapshot and starting up the old 2.0.10 again. Does anyone have an idea how this can be fixed? Thanks, Tom ERROR 13:51:57 Exception encountered during startup org.apache.cassandra.serializers.MarshalException: unable to make version 1 UUID from 'currencyCode' at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:188) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.marshal.AbstractCompositeType.fromString(AbstractCompositeType.java:242) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.ColumnDefinition.fromSchema(ColumnDefinition.java:397) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.CFMetaData.fromSchemaNoTriggers(CFMetaData.java:1750) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1860) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:321) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:302) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.DefsTables.loadFromKeyspace(DefsTables.java:133) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:696) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:672) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:293) [apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:536) [apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:625) [apache-cassandra-2.1.6.jar:2.1.6] Caused by: org.apache.cassandra.serializers.MarshalException: unable to coerce 'currencyCode' to a formatted date (long) at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:111) ~[apache-cassandra-2.1.6.jar:2.1.6] at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:184) ~[apache-cassandra-2.1.6.jar:2.1.6] ... 12 common frames omitted Caused by: java.text.ParseException: Unable to parse the date: currencyCode at org.apache.commons.lang3.time.DateUtils.parseDateWithLeniency(DateUtils.java:336) ~[commons-lang3-3.1.jar:3.1] at org.apache.commons.lang3.time.DateUtils.parseDateStrictly(DateUtils.java:286) ~[commons-lang3-3.1.jar:3.1] at org.apache.cassandra.serializers.TimestampSerializer.dateStringToTimestamp(TimestampSerializer.java:107) ~[apache-cassandra-2.1.6.jar:2.1.6] ... 13 common frames omitted org.apache.cassandra.serializers.MarshalException: unable to make version 1 UUID from 'currencyCode' at org.apache.cassandra.db.marshal.UUIDType.fromString(UUIDType.java:188) at org.apache.cassandra.db.marshal.AbstractCompositeType.fromString(AbstractCompositeType.java:242) at org.apache.cassandra.config.ColumnDefinition.fromSchema(ColumnDefinition.java:397) at org.apache.cassandra.config.CFMetaData.fromSchemaNoTriggers(CFMetaData.java:1750) at org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1860) at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:321) at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:302) at org.apache.cassandra.db.DefsTables.loadFromKeyspace(DefsTables.java:133) at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:696) at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:672) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:293) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:536) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:625) Caused by: org.apache.cassandra.serializers.MarshalException: unable to coerce 'currencyCode' to a formatted date (long) at
