cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3954) Exceptions during start up after schema disagreement
Date Thu, 15 Mar 2012 22:04:38 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Yaskevich updated CASSANDRA-3954:
---------------------------------------

    Attachment:     (was: CASSANDRA-3954-v2.patch)
    
> Exceptions during start up after schema disagreement
> ----------------------------------------------------
>
>                 Key: CASSANDRA-3954
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3954
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Mariusz
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1.0
>
>         Attachments: CASSANDRA-3954.patch
>
>
> Hi,
> i`ve got schema disaggreement after dropping down keyspace,
> i`ve switched off one nodes in cluster, after starting i`ve got bunch of these exceptions:
> {code}
> ERROR [SSTableBatchOpen:1] 2012-02-24 14:21:00,759 AbstractCassandraDaemon.java (line
134) Fatal exception in thread Thread[SSTableBatchOpen:1,5,main]
> java.lang.ClassCastException: java.math.BigInteger cannot be cast to java.nio.ByteBuffer
>         at org.apache.cassandra.db.marshal.UTF8Type.compare(UTF8Type.java:27)
>         at org.apache.cassandra.dht.LocalToken.compareTo(LocalToken.java:45)
>         at org.apache.cassandra.db.DecoratedKey.compareTo(DecoratedKey.java:89)
>         at org.apache.cassandra.db.DecoratedKey.compareTo(DecoratedKey.java:38)
>         at java.util.TreeMap.getEntry(TreeMap.java:328)
>         at java.util.TreeMap.containsKey(TreeMap.java:209)
>         at java.util.TreeSet.contains(TreeSet.java:217)
>         at org.apache.cassandra.io.sstable.SSTableReader.load(SSTableReader.java:393)
>         at org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:189)
>         at org.apache.cassandra.io.sstable.SSTableReader$1.run(SSTableReader.java:227)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)
> {code}
> and this one on the end of start up:
> {code}
> ERROR [MigrationStage:1] 2012-02-24 14:37:22,750 AbstractCassandraDaemon.java (line 134)
Fatal exception in thread Thread[MigrationStage:1,5,main]
> java.lang.NullPointerException
>         at org.apache.cassandra.db.migration.MigrationHelper.addColumnFamily(MigrationHelper.java:282)
>         at org.apache.cassandra.db.migration.MigrationHelper.addColumnFamily(MigrationHelper.java:216)
>         at org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:330)
>         at org.apache.cassandra.db.DefsTable.mergeRemoteSchema(DefsTable.java:240)
>         at org.apache.cassandra.service.MigrationManager$1.runMayThrow(MigrationManager.java:124)
>         at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)
> {code}
> Any ideas why they`ve appeared?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message