[
https://issues.apache.org/jira/browse/CASSANDRA-16815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390683#comment-17390683
]
Yifan Cai commented on CASSANDRA-16815:
---------------------------------------
I think it is a valid concern.
Thinking about it a bit more. A config (init from cassandra.yaml and modifiable
via JMX) to set the duration until a hint to be cleaned up is better than a
simple boolean toggle. The default can be 0, meaning there is no scheduled
cleanup job to delete the files. It is the same behavior w/o the patch.
When to delete the hints is workflow dependent. Some team might have the
workflow to keep the invalid hints as you pointed out. Some team would like to
automatically delete the invalid ones to reclaim space and reduce the ops
burden. Providing such a config field and let the operators to decide based on
their experience would be flexible and convenient.
> Background schedule to clean up orphaned hints files
> ----------------------------------------------------
>
> Key: CASSANDRA-16815
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16815
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Other
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Host replacement is possible to produce orphaned hints files that the
> original associated host ID no longer exist in the cluster (i.e., being
> replaced). Those orphaned hints files will not be dispatched and only
> consumes up the disk space.
> We can have a background schedule that infrequently checks and deletes the
> files if they are orphaned and have exceeded the TTL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
