You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Roth (JIRA)" <ji...@apache.org> on 2016/08/24 12:28:20 UTC
[jira] [Created] (CASSANDRA-12530) NPE in MutationStage after
WriteTimeoutException
Benjamin Roth created CASSANDRA-12530:
-----------------------------------------
Summary: NPE in MutationStage after WriteTimeoutException
Key: CASSANDRA-12530
URL: https://issues.apache.org/jira/browse/CASSANDRA-12530
Project: Cassandra
Issue Type: Bug
Components: Local Write-Read Paths
Reporter: Benjamin Roth
I observed a situation where nodes seem to be overloaded by MV updates (probably). This produces tons of exceptions like the following.
I guess the WriteTimeoutExceptions come from updates on remote hosts during the MV-write-path. So far so good - shit happens in an overloaded system. But the following NPE is probably not really intended and a follow-up exception of the timed out write.
2016-08-24T12:22:45+00:00 cas5 [MutationStage-25] org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService Uncaught exception on thread Thread[MutationStage-25,5,main]: {}
2016-08-24T12:22:45+00:00 cas5 #011org.apache.cassandra.exceptions.WriteTimeoutException: Operation timed out - received only 0 responses.
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:486)
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.db.Keyspace.lambda$apply$0(Keyspace.java:495)
2016-08-24T12:22:45+00:00 cas5 #011at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109)
2016-08-24T12:22:45+00:00 cas5 #011at java.lang.Thread.run(Thread.java:745)
2016-08-24T12:22:45+00:00 cas5 [MutationStage-31] org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService Uncaught exception on thread Thread[MutationStage-31,5,main]: {}
2016-08-24T12:22:45+00:00 cas5 #011org.apache.cassandra.exceptions.WriteTimeoutException: Operation timed out - received only 0 responses.
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:486)
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.db.Keyspace.lambda$apply$0(Keyspace.java:495)
2016-08-24T12:22:45+00:00 cas5 #011at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
2016-08-24T12:22:45+00:00 cas5 #011at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109)
2016-08-24T12:22:45+00:00 cas5 #011at java.lang.Thread.run(Thread.java:745)
2016-08-24T12:22:45+00:00 cas5 [MutationStage-7] org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService Uncaught exception on thread Thread[MutationStage-7,5,main]: {}
2016-08-24T12:22:45+00:00 cas5 #011java.lang.NullPointerException: null
2016-08-24T12:22:45+00:00 cas5 [MutationStage-32] org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService Uncaught exception on thread Thread[MutationStage-32,5,main]: {}
2016-08-24T12:22:45+00:00 cas5 #011java.lang.NullPointerException: null
2016-08-24T12:22:45+00:00 cas5 [MutationStage-9] org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService Uncaught exception on thread Thread[MutationStage-9,5,main]: {}
2016-08-24T12:22:45+00:00 cas5 #011java.lang.NullPointerException: null
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)