[
https://issues.apache.org/jira/browse/CASSANDRA-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077429#comment-14077429
]
Benedict commented on CASSANDRA-7582:
-------------------------------------
We can add some explanation in the error message, suggesting that in the event
of power failure it is safe to ignore these errors, and can also make them more
robust under power failure (e.g. we could write a check-summed value instead of
zeros to the next marker on completion of sync, which differs from the marker
present once the next section has begun writing, so that we can ignore any
errors occurring on a section without a fully-synced marker). The exception in
general can mention that the message is _likely_ the result of corruption,
either from power or hardware failure. As an end user I would still prefer in
this scenario to know that it happened, and opt-in to repairing it by ignoring
the errors.
What hole are we talking about? We *shouldn't* in any version of C* see any CL
records for dropped tables since we checkpoint and discard the commit log after
a DROP. So we'd only see this message if there's a bug anyway, unless you're
using PIT restore.
> 2.1 multi-dc upgrade errors
> ---------------------------
>
> Key: CASSANDRA-7582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7582
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Ryan McGuire
> Assignee: Benedict
> Priority: Critical
> Fix For: 2.1.1
>
>
> Multi-dc upgrade [was working from 2.0 -> 2.1 fairly
> recently|http://cassci.datastax.com/job/cassandra_upgrade_dtest/55/testReport/upgrade_through_versions_test/TestUpgrade_from_cassandra_2_0_latest_tag_to_cassandra_2_1_HEAD/],
> but is currently failing.
> Running
> upgrade_through_versions_test.py:TestUpgrade_from_cassandra_2_0_HEAD_to_cassandra_2_1_HEAD.bootstrap_multidc_test
> I get the following errors when starting 2.1 upgraded from 2.0:
> {code}
> ERROR [main] 2014-07-21 23:54:20,862 CommitLog.java:143 - Commit log replay
> failed due to replaying a mutation for a missing table. This error can be
> ignored by providing -Dcassandra.commitlog.stop_on_missing_tables=false on
> the command line
> ERROR [main] 2014-07-21 23:54:20,869 CassandraDaemon.java:474 - Exception
> encountered during startup
> java.lang.RuntimeException:
> org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find
> cfId=a1b676f3-0c5d-3276-bfd5-07cf43397004
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:300)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:457)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:546)
> [main/:na]
> Caused by: org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't
> find cfId=a1b676f3-0c5d-3276-bfd5-07cf43397004
> at
> org.apache.cassandra.db.ColumnFamilySerializer.deserializeCfId(ColumnFamilySerializer.java:164)
> ~[main/:na]
> at
> org.apache.cassandra.db.ColumnFamilySerializer.deserialize(ColumnFamilySerializer.java:97)
> ~[main/:na]
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserializeOneCf(Mutation.java:353)
> ~[main/:na]
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:333)
> ~[main/:na]
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:365)
> ~[main/:na]
> at
> org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:98)
> ~[main/:na]
> at
> org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:137)
> ~[main/:na]
> at
> org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:115)
> ~[main/:na]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
