You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2019/12/06 21:40:00 UTC

[jira] [Commented] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

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

David Capwell commented on CASSANDRA-15444:
-------------------------------------------

Reworded to reflect the issue is local to StandaloneUpgrader and not CassandraDaemon (which detects this in StartupCheck)

> When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-15444
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15444
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Startup and Shutdown
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>
> If you start up with old SSTables that are no longer supported, the daemon should shutdown to avoid accidental data loss; currently the behavior is to silently (no log) skip these files which leads to data loss.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org