You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/06/28 12:46:00 UTC
[jira] [Updated] (CASSANDRA-16767) Add user defined SSTables option
for nodetool garbagecollect
[ https://issues.apache.org/jira/browse/CASSANDRA-16767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-16767:
-----------------------------------------
Change Category: Operability
Complexity: Normal
Component/s: Tool/sstable
Fix Version/s: 3.11.x
Status: Open (was: Triage Needed)
> Add user defined SSTables option for nodetool garbagecollect
> ------------------------------------------------------------
>
> Key: CASSANDRA-16767
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16767
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/sstable
> Reporter: Scott Carey
> Assignee: Scott Carey
> Priority: Normal
> Fix For: 3.11.x
>
>
> nodetool garbagecollect does not yet have an option to supply a user defined list of SSTables to process.
> This is unfortunate, because there are many cases where an operator would know which subset of tables are in need of a garbagecollect. Perhaps with STCS, one would choose to garbagecollect only the largest file.
> With a large LCS table, it is typical that the highest levels have the most overwritten data, and it may take a very long time to run a full garbagecollect or full compaction, but a relatively short time to process a smaller subset of SSTables.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org