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/04/03 09:08:00 UTC
[jira] [Updated] (CASSANDRA-18408) CEP-21 Implement retries for log replay on CMS members
[ https://issues.apache.org/jira/browse/CASSANDRA-18408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-18408:
----------------------------------------
Change Category: Semantic
Complexity: Normal
Component/s: Transactional Cluster Metadata
Reviewers: Marcus Eriksson, Sam Tunnicliffe
Assignee: Alex Petrov (was: Sam Tunnicliffe)
Status: Open (was: Triage Needed)
https://github.com/beobal/cassandra/commit/d4fb51f8591822367fcde895db5c278d238381e0
> CEP-21 Implement retries for log replay on CMS members
> ------------------------------------------------------
>
> Key: CASSANDRA-18408
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18408
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Alex Petrov
> Priority: Normal
>
> This should enable {{AbstractLocalProcessor}} implementations to backoff and retry when executing distributed reads of the consistent log, in much the same way that {{RemoteProcessor}} does when making replay requests to CMS members.
--
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