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

Stefan Miklosovic commented on CASSANDRA-17147:
-----------------------------------------------

[~adelapena] would you mind to elaborate on CASSANDRA-17180 in the light of the 
proposed patch? Do you think if that is feasible?

One thing I am not sure about is that where we do a "cut" between guardrails 
and startup checks. As I went through the patch, it seems to me that the 
guardrails framework is "request oriented", having ClientState passed around 
and so on. I do not want that nor I need that for tasks related to startup of 
the node. How is this framework coping with it?

> 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: 19h 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