[ https://issues.apache.org/jira/browse/CASSANDRA-20142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Petrov updated CASSANDRA-20142: ------------------------------------ Fix Version/s: 5.1 Since Version: 5.1-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/e9afe9539a7f67cf0efae771100f5a3f69cef637 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Fix topology replay during bootstrap and startup, decouple Accord from TCM > -------------------------------------------------------------------------- > > Key: CASSANDRA-20142 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20142 > Project: Apache Cassandra > Issue Type: Bug > Components: Accord > Reporter: Alex Petrov > Assignee: Alex Petrov > Priority: Normal > Fix For: 5.1 > > Attachments: ci_summary-1.html, ci_summary.html > > > Includes multiple changes, primary ones: > * Removed nodes now live in TCM, no need to discover historic epochs in > order to find removed nodes > * CommandStore <-> RangesForEpochs mappings required for startup are now > stored in journal, and CS can be set up _without_ topology replay > * Topology replay is fully done via journal (where we store topologies > themselves), and topology metadata table (where we store redundant/closed > information) > * Fixed various bugs related to propagation and staleness > * TCM was previously relied on for "fetching" epoch: we can not rely on > it as there's no guarantee we will see a consecutive epoch when grabbing > Metadata#current > * Redundant / closed during replay was set with incorrect ranges in 1 of > the code paths > * TCM was contacted multiple times for historical epochs, which made > startup much longer under some circumstances -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org