You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (Jira)" <ji...@apache.org> on 2023/07/24 12:18:00 UTC
[jira] [Updated] (CASSANDRA-18458) CEP-21 During startup, don't open SSTables until local metadata log replay is complete
[ https://issues.apache.org/jira/browse/CASSANDRA-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-18458:
----------------------------------------
Fix Version/s: NA
Source Control Link: https://github.com/apache/cassandra/commit/633b40766b046cd852f312e51c4b6dbc60e49add
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> CEP-21 During startup, don't open SSTables until local metadata log replay is complete
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18458
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18458
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: NA
>
>
> Eagerly opening SSTables when their {{ColumnFamilyStore}} is first instantiated presents problems when replaying the local metadata log during startup. Schema modifications which _had_ been applied by the time an SSTable was written may not have been replayed yet, causing serialization errors. To address this, we can defer opening SSTables until after the local log replay is complete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org