[ 
https://issues.apache.org/jira/browse/CASSANDRA-10738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023261#comment-15023261
 ] 

cs commented on CASSANDRA-10738:
--------------------------------

(ignoring the concept of 'unlucky')

can you suggest which schema snapshots to restore in this instance? in v2 they 
are:

../data/system/schema_*/

and in v3 they are

../data/system_schema/indexes-*/

you suggest keyspaces in the 2nd to last comment, but the log indicates 
indexes. which sstables from v2 map to the equivalent failing 
system_schema/indexes-*/ tables in v3? or is there a reason you suggest 
system_schema.keyspaces?

> upgrading to v3.0.0 nodes crashes with 
> "org.apache.cassandra.serializers.MarshalException: Unexpected extraneous 
> bytes after map value"
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10738
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10738
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: ubuntu14, java8
>            Reporter: cs
>            Assignee: Aleksey Yeschenko
>         Attachments: cassv3.txt
>
>
> upgrading from v.2.2.3 to v3.0.0
> restarting after upgrade crashes with either
> ERROR [main] 2015-11-19 20:21:26,511 CassandraDaemon.java:702 - Exception 
> encountered during startup
> org.apache.cassandra.serializers.MarshalException: Unexpected extraneous 
> bytes after map value
> OR 
> ERROR [main] 2015-11-19 20:01:13,945 CassandraDaemon.java:702 - Exception 
> encountered during startup
> java.lang.IllegalArgumentException: null
> see attached debug and schema



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to