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

Ekaterina Dimitrova commented on CASSANDRA-17147:
-------------------------------------------------

{quote}[~e.dimitrova] will solve all problems!
{quote}
Only putting general framework, if I strive for "all problems" we will never 
commit that work :D 

About "fail" and "abort" I haven't thought about or discussed this. It was more 
of a liberations the parameters names from the suffixes and have a common 
format noun_verb, things like that :) But I would be happy to address this 
topic too when the time comes. 
{quote} [~e.dimitrova], if this ticket goes in before CASSANDRA-15234 don't 
worry about "fixing" the configs, we can pick that up in January after the fact.
{quote}
Thank you! My plan Is no rebase until we are done with the current review cycle 
as otherwise it becomes never ending story, running in circles. 

> Guardrails prototype
> --------------------
>
>                 Key: CASSANDRA-17147
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17147
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Feature/Guardrails
>            Reporter: Andres de la Peña
>            Assignee: Andres de la Peña
>            Priority: Normal
>             Fix For: 4.x
>
>          Time Spent: 14h 50m
>  Remaining Estimate: 0h
>
> The purpose of this ticket is creating an initial implementation of the 
> guardrails framework, as well as adding a few simple guardrails using this 
> framework.
> To keep things easy, this initial implementation would only support 
> guardrails that are triggered on the coordinator, and they would be 
> dynamically updatable only through JMX.
> Once we have this initial framework ready in a feature branch we can have 
> multiple tickets addressing all the things that would have been left out of 
> the scope of this ticket, such as:
> * Dynamic updates through virtual tables
> * Being able to notify about guardrails triggered on replicas
> * Using custom exceptions other than {{InvalidRequestException}}.
> * Porting existing limits to use the new guardrails framework
> * Adding new guardrails beyond the initial ones
> The reason for having this simpler prototype is that it will give us a common 
> ground to parallelize work on the parts mentioned above.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to