cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8049) Explicitly examine current C* state on startup to detect incompatibilities before upgrade
Date Tue, 05 May 2015 20:57:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Tunnicliffe updated CASSANDRA-8049:
---------------------------------------
    Attachment: 8049-follow-up.txt

New version of the follow up patch, as I missed a new test data file from the first one.

> 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-follow-up.txt, 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)

Mime
View raw message