cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wansbrough (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12424) Assertion failure in ViewUpdateGenerator
Date Tue, 16 Aug 2016 09:50:20 GMT

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

Keith Wansbrough commented on CASSANDRA-12424:
----------------------------------------------

FWIW: I renamed /var/lib/cassandra/commitlog/ and recreated it as an empty directory, and
Cassandra started OK.

> Assertion failure in ViewUpdateGenerator
> ----------------------------------------
>
>                 Key: CASSANDRA-12424
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12424
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Keith Wansbrough
>            Assignee: Carl Yeksigian
>         Attachments: cassandra.log
>
>
> Using released apache-cassandra-3.7.0, we have managed to get a node into a state where
it won't start up. The exception is {{java.lang.AssertionError: We shouldn't have got there
is the base row had no associated entry}} and it appears in ViewUpdateGenerator.computeLivenessInfoForEntry(ViewUpdateGenerator.java:455).
> I still have the offending node; what diags/data would be useful for diagnosis? I've
attached the full cassandra.log. In summary, cassandra.log contains multiple instances of
the following when replaying the commit log on startup, leading ultimately to failure to start
up.
> {code}
> ERROR 15:24:17 Unknown exception caught while attempting to update MaterializedView!
edison.scs_subscriber
> java.lang.AssertionError: We shouldn't have got there is the base row had no associated
entry
>         at org.apache.cassandra.db.view.ViewUpdateGenerator.computeLivenessInfoForEntry(ViewUpdateGenerator.java:455)
~[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.view.ViewUpdateGenerator.updateEntry(ViewUpdateGenerator.java:273)
~[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.view.ViewUpdateGenerator.addBaseTableUpdate(ViewUpdateGenerator.java:127)
~[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.view.TableViews.addToViewUpdateGenerators(TableViews.java:403)
~[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.view.TableViews.generateViewUpdates(TableViews.java:236)
~[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.view.TableViews.pushViewReplicaUpdates(TableViews.java:140)
~[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:514) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.Keyspace.applyFromCommitLog(Keyspace.java:409) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.commitlog.CommitLogReplayer$MutationInitiator$1.runMayThrow(CommitLogReplayer.java:152)
[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) [apache-cassandra-3.7.0.jar:3.7.0]
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_91]
>         at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
[apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) [apache-cassandra-3.7.0.jar:3.7.0]
>         at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> WARN  15:24:17 Uncaught exception on thread Thread[SharedPool-Worker-4,5,main]: {}
> {code}
> and ultimately 
> {code}
> ERROR 15:24:18 Exception encountered during startup
> java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.AssertionError:
We shouldn't have got there is the base row had no associated entry
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message