You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Carl Yeksigian (JIRA)" <ji...@apache.org> on 2012/12/09 00:05:21 UTC

[jira] [Updated] (CASSANDRA-4984) error opening data file at startup

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

Carl Yeksigian updated CASSANDRA-4984:
--------------------------------------

    Attachment: 4984.patch
    
> error opening data file at startup
> ----------------------------------
>
>                 Key: CASSANDRA-4984
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4984
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.6
>         Environment: Oracle Java 1.6u37
>            Reporter: Zenek Kraweznik
>         Attachments: 4984.patch
>
>
> I've found this in logfile, this happens at cassandra startup:
> INFO 10:06:13,670 Opening /var/lib/cassandra/data/MYKSPC/MYCF/MYKSPC-MYCF-hf-5547 (1073761823 bytes)
> ERROR 10:06:13,670 Exception in thread Thread[SSTableBatchOpen:3,5,main]
> java.lang.AssertionError
>         at org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:166)
>         at org.apache.cassandra.io.sstable.SSTableReader.open(SSTableReader.java:153)
>         at org.apache.cassandra.io.sstable.SSTableReader$1.run(SSTableReader.java:242)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>         at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>         at java.util.concurrent.FutureTask.run(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>         at java.lang.Thread.run(Unknown Source)
> Every CF in this Keyspace has cashing set to 'NONE'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira