You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mark Robson (JIRA)" <ji...@apache.org> on 2009/04/30 18:34:30 UTC
[jira] Created: (CASSANDRA-124) NullPointerException in consistency
manager after a failed node rejoins
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
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.
[jira] Updated: (CASSANDRA-124) NullPointerException in consistency
manager after a failed node rejoins
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-124:
-------------------------------------
Fix Version/s: 0.3
Priority: Critical (was: Major)
> 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.
[jira] Commented: (CASSANDRA-124) NullPointerException in
consistency manager after a failed node rejoins
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705615#action_12705615 ]
Jonathan Ellis commented on CASSANDRA-124:
------------------------------------------
Oops, I take it back. It's a regression from CASSANDRA-95. nk11 is right, the constructor got broken.
> 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.
[jira] Commented: (CASSANDRA-124) NullPointerException in
consistency manager after a failed node rejoins
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705613#action_12705613 ]
Jonathan Ellis commented on CASSANDRA-124:
------------------------------------------
FWIW this is not a regression, it's only showing up in the logs now after I added a change that logs exceptions from our executors instead of ignoring them.
> 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.
[jira] Resolved: (CASSANDRA-124) NullPointerException in
consistency manager after a failed node rejoins
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-124.
--------------------------------------
Resolution: Fixed
Assignee: Jonathan Ellis
looks fixed in my testing
> 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
> Assignee: Jonathan Ellis
> 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.
[jira] Commented: (CASSANDRA-124) NullPointerException in
consistency manager after a failed node rejoins
Posted by "nk11 (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705309#action_12705309 ]
nk11 commented on CASSANDRA-124:
--------------------------------
Shouldn't ConsistencyManager() constructor contain the following line?
this.replicas_ = replicas_;
> 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.
[jira] Commented: (CASSANDRA-124) NullPointerException in
consistency manager after a failed node rejoins
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.