cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-995) restarting node crashes with NPE when, while replaying the commitlog, the cfMetaData is requested
Date Fri, 16 Apr 2010 20:57:27 GMT

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

Jonathan Ellis updated CASSANDRA-995:
-------------------------------------

    Fix Version/s: 0.7
         Priority: Critical  (was: Major)
      Component/s: Core

> restarting node crashes with NPE when, while replaying the commitlog, the cfMetaData
is requested
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-995
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-995
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7
>         Environment: SVN rev 935070
>            Reporter: Ted Zlatanov
>            Assignee: Gary Dusbabek
>            Priority: Critical
>             Fix For: 0.7
>
>
> Removing the commitlog directory completely fixes this.   I can reliably reproduce it
by 1) starting and configuring a schema with one keyspace, one super CF with LongType supercolumns;
2) inserting data; 3) shutting down and restarting the node.
> Here's my schema expressed in cassidy.pl, should be obvious what the parameters are:
> ./cassidy.pl -server X -port Y -keyspace system 'kdefine test org.apache.cassandra.locator.RackUnawareStrategy
2 org.apache.cassandra.locator.EndPointSnitch'
> ./cassidy.pl -server X -port Y -keyspace test 'fdefine Status Super LongType BytesType
comment=statuschanges,row_cache_size=0,key_cache_size=20000'
> The problem seems to be related to CASSANDRA-44 as it happens when the CF metadata is
requested but I don't know what's causing it.
> 10/04/16 15:25:11 INFO commitlog.CommitLog: Replaying /home/cassandra/commitlog/CommitLog-1271449410100.log,
/home/cassandra/commitlog/CommitLog-1271449378151.log, /home/cassandra/commitlog/CommitLog-1271449415800.log
> java.lang.reflect.InvocationTargetException
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:160)
> Caused by: java.lang.NullPointerException
>         at org.apache.cassandra.db.Table.<init>(Table.java:261)
>         at org.apache.cassandra.db.Table.open(Table.java:102)
>         at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:233)
>         at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:172)
>         at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:104)
>         at org.apache.cassandra.thrift.CassandraDaemon.init(CassandraDaemon.java:151)
>         ... 5 more

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

        

Mime
View raw message