[jira] [Commented] (CASSANDRA-19482) Simplify metadata log implementation using custom partitioner

["Sam Tunnicliffe (Jira)" <ji...@apache.org>]

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

Sam Tunnicliffe commented on CASSANDRA-19482:
---------------------------------------------

I've addressed the comments on the PR and also made further changes to support running repair on the {{system_cluster_metadata}} keyspace.
Updated CI results attached, tl;dr the handful of failures either already have JIRAs (CASSANDRA-19538) or are suspected to be due to CASSANDRA-19514.

> Simplify metadata log implementation using custom partitioner
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-19482
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19482
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Transactional Cluster Metadata
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 5.x
>
>         Attachments: ci_summary.html, result_details.tar.gz
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The distributed metadata log table can be simplified by leveraging the fact that replicas are all responsible for the entire token range. Given this assumption, we can then use {{ReversedLongLocalPartitioner}} introduced in CASSANDRA-19391 to make it much easier to append to/read from the tail of the log, effectively removing the need for the {{Period}} construct. This will also improve apply to the local metadata log used at startup.  



--
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