[
https://issues.apache.org/jira/browse/CASSANDRA-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456703#comment-17456703
]
Yifan Cai commented on CASSANDRA-17142:
---------------------------------------
PR: https://github.com/apache/cassandra/pull/1357
CI:
https://app.circleci.com/pipelines/github/yifan-c/cassandra/288/workflows/566bde90-9b69-4743-9e12-a97d4a4c137a
(mostly green)
As mentioned in the description, the PR add the configuration,
{{max_hints_size_per_host_in_mb}}, to limit the total size of the hints per
host. It is off by default.
Thanks [~Gerrrr] for bringing up the Guardrails framework. Read though the CEP
and the first merged prototype. I think ultimately it is a good fit as you
mentioned. But as of now, the implementation is client facing since its
foundation classes depends on ClientState and ClientWarn. It does not fit very
well with those system-internal limits. I can see Guardrails is approaching it
iteratively. With respect to this ticket, we do not have to block it. We can
merge it first and address the required refactoring along with the other
system-internal limits when Guardrails evolves.
> Limit the maximum hints size per host
> -------------------------------------
>
> Key: CASSANDRA-17142
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17142
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Hints
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
>
> The hints system defines a time window, i.e. max_hint_window_in_ms, to store
> the hints.
> It defines no limit on how much data can be kept during the time window. The
> hints can grow excessively and make the node running out of disk. In such
> scenario, the operators have to truncate the hints manually.
> I'd propose that in addition to the conventional hints window, operators
> should be able to define the maximum hints size per host, i.e.
> max_hints_size_per_host_in_mb, to provide an another layer of protection. A
> node stops to store hints for the down node whenever it reaches to the time
> cap or the size cap. In order to not surprise the users, the config should be
> disabled by default. It should also be configurable via JMX.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
