You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict Elliott Smith (Jira)" <ji...@apache.org> on 2021/10/06 13:08:00 UTC

[jira] [Updated] (CASSANDRA-17024) Artificial Latency Injection

     [ https://issues.apache.org/jira/browse/CASSANDRA-17024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict Elliott Smith updated CASSANDRA-17024:
-----------------------------------------------
    Change Category: Semantic
         Complexity: Normal
      Fix Version/s: 4.x
             Status: Open  (was: Triage Needed)

> Artificial Latency Injection
> ----------------------------
>
>                 Key: CASSANDRA-17024
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17024
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Messaging/Internode
>            Reporter: Benedict Elliott Smith
>            Assignee: Benedict Elliott Smith
>            Priority: Normal
>             Fix For: 4.x
>
>
> *Motivation*
> Cassandra aims to enable user’s applications to continue to function in the presence of major incidents. To support this clusters must support high-availability topologies, i.e. at present at least 3 DCs at remote distances from each other. Operators wanting to migrate clusters initially created in topologies that do not support this capability, or to move from LOCAL_X to (GLOBAL) X consistency levels, have no mechanism for determining the viability of the strategy for their applications. This is particularly critical for applications that use LWTs, for which the degradation may be unpredictable due to contention effects.
> *Goals*
> Support cluster-wide latency injection for some subset of messages 
> User Impact
> *User Impact*
> Users will be able to specify the set of Verbs that should be affected, and also which queries within their client-side application. 
> Clients will be supported by the introduction of new {{UNSAFE_DELAY_X}} consistency levels that mark queries as suitable to experience additional artificial latency. 
> Latency will be controlled by JMX properties specifying whether only {{UNSAFE_DELAY_X}} operations are affected, alongside which verbs and the length of the delay.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org