cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-124) NullPointerException in consistency manager after a failed node rejoins
Date Tue, 05 May 2009 13:44:30 GMT

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

Hudson commented on CASSANDRA-124:
----------------------------------

Integrated in Cassandra #59 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/59/])
    do not leave variables uninitialized in ConsistencyManager constructor.  fixes regression
from #95.  patch by jbellis for 


> NullPointerException in consistency manager after a failed node rejoins
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-124
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-124
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: trunk
>         Environment: Centos 5.0 java version "1.6.0_13"
>            Reporter: Mark Robson
>            Priority: Critical
>             Fix For: 0.3
>
>
> ERROR [CONSISTENCY-MANAGER:2] 2009-04-30 18:22:38,946 DebuggableThreadPoolExecutor.java
(line 89) Error in ThreadPoolExecutor
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
>         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:83)
>         at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.afterExecute(DebuggableThreadPoolExecutor.java:65)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:888)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.NullPointerException
>         at org.apache.cassandra.service.ConsistencyManager.run(ConsistencyManager.java:168)
>         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)
>         ... 2 more
> Plus other similar ones.
> Config:
>     <ReplicationFactor>2</ReplicationFactor>
>     <Tables>
>         <Table Name="Messages">
>             <ColumnFamily ColumnSort="Name" Name="base"/>
>             <ColumnFamily ColumnSort="Name" Name="extra"/>
>             <ColumnFamily ColumnSort="Time" Name="StandardByTime1"/>
>             <ColumnFamily ColumnSort="Time" Name="StandardByTime2"/>
>             <ColumnFamily ColumnType="Super" ColumnSort="Name" Name="Super1"/>
>             <ColumnFamily ColumnType="Super" ColumnSort="Name" Name="Super2"/>
>         </Table>
>     </Tables>
> I inserted some data using insert method on another node while one node had failed (of
three), then brought the failed node back

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message