[jira] [Commented] (CASSANDRA-8049) Explicitly examine current C* state on startup to detect incompatibilities before upgrade

["Tyler Hobbs (JIRA)" <ji...@apache.org>]

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

Tyler Hobbs commented on CASSANDRA-8049:
----------------------------------------

Snapshot manifest files ({{manifest.json}}) are triggering the "unreadable sstables" check, which is causing a lot of dtest failures (e.g. [snapshot tests|http://cassci.datastax.com/job/trunk_dtest/62/testReport/junit/snapshot_test/TestArchiveCommitlog/dont_test_archive_commitlog_4/]).  It seems like that check should ignore files without a {{.db}} extension, correct?

> Explicitly examine current C* state on startup to detect incompatibilities before upgrade
> -----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8049
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8049
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Sam Tunnicliffe
>             Fix For: 3.0
>
>         Attachments: 8049-v2.txt, 8049.txt
>
>
> Unfortunately, we cannot rely on users reading, and following, NEWS.txt before upgrading. People don't read, or ignore it, and sometimes have issues as the result (see CASSANDRA-8047, for example, and I know of several cases like that one).
> We should add an explicit compatibility check on startup, before we modify anything, or write out sstables with the new format. We should fail and complain loudly if we detect a skipped upgrade step.
> We should also snapshot the schema tables before attempting any conversions (since it's not uncommon to make schema modifications as part of the upgrade).



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