You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2020/08/11 07:35:00 UTC
[jira] [Updated] (CASSANDRA-16043) Perform garbage collection on
specific partitions or range of partitions
[ https://issues.apache.org/jira/browse/CASSANDRA-16043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-16043:
----------------------------------------
Change Category: Operability
Complexity: Normal
Component/s: Local/Compaction
Fix Version/s: 4.x
Status: Open (was: Triage Needed)
> Perform garbage collection on specific partitions or range of partitions
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-16043
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16043
> Project: Cassandra
> Issue Type: New Feature
> Components: Local/Compaction
> Reporter: Johnny Miller
> Priority: Normal
> Fix For: 4.x
>
>
> Some of our data is quite seasonal and variable based on partitions and certain partitions tend to contain significantly more tombstones than others. We currently run nodetool garbagecollect on tables when this becomes an issue.
> However, if the time to complete and resources required to only garbage collect particular partitions on specific tables could improve the performance of this activity it would be useful to only target the specific partitions we need.
--
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