You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex Petrov (Jira)" <ji...@apache.org> on 2024/08/07 14:20:00 UTC
[jira] [Updated] (CASSANDRA-19790) Add an ability to reconstruct arbitrary epoch state from the log to TCM
[ https://issues.apache.org/jira/browse/CASSANDRA-19790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Petrov updated CASSANDRA-19790:
------------------------------------
Change Category: Semantic
Complexity: Normal
Component/s: Transactional Cluster Metadata
Fix Version/s: 5.1
Priority: High (was: Normal)
Status: Open (was: Triage Needed)
> Add an ability to reconstruct arbitrary epoch state from the log to TCM
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-19790
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19790
> Project: Cassandra
> Issue Type: New Feature
> Components: Transactional Cluster Metadata
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: High
> Fix For: 5.1
>
>
> Current Accord functionality requires TCM to be able to provide cluster metadata for an arbitrary epoch. Unfortunately, epochs are not always available locally especially on bootstrapping non-CMS nodes. For this, we need to reconstruct from the log.
--
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