[
https://issues.apache.org/jira/browse/CASSANDRA-17142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Guerrero updated CASSANDRA-17142:
-------------------------------------------
Reviewers: Francisco Guerrero
Status: Review In Progress (was: Patch Available)
Reviewing PR in GitHub
> 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
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
