[
https://issues.apache.org/jira/browse/CASSANDRA-18402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-18402:
----------------------------------------
Change Category: Semantic
Complexity: Normal
Component/s: Transactional Cluster Metadata
Reviewers: Marcus Eriksson, Sam Tunnicliffe
Status: Open (was: Triage Needed)
https://github.com/beobal/cassandra/commit/81b90d47290f1602b9d3b78b6e413d05d8750758
> CEP-21 Add debounce to log replay
> ---------------------------------
>
> Key: CASSANDRA-18402
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18402
> Project: Cassandra
> Issue Type: New Feature
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
>
> To avoid overload we should debounce log replay requests between non-CMS
> nodes and CMS members. If a non-CMS node already has a replay request
> inflight, any subsequent requests should wait for the inflight response and
> return that. As soon as a response has been received, that request should be
> considered stale and a new one initiated.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
