You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/09/16 22:07:20 UTC

[jira] [Created] (KUDU-1625) Schedule compaction on rowsets with high percentage of deleted data

Todd Lipcon created KUDU-1625:
---------------------------------

             Summary: Schedule compaction on rowsets with high percentage of deleted data
                 Key: KUDU-1625
                 URL: https://issues.apache.org/jira/browse/KUDU-1625
             Project: Kudu
          Issue Type: Improvement
          Components: tablet
    Affects Versions: 1.0.0
            Reporter: Todd Lipcon


Although with KUDU-236 we can now remove rows that were deleted prior to the ancient history mark, we don't actively schedule compactions based on deleted rows. So, if for example we have a fully compacted table and issue a DELETE for every row, the data size actually does not change, because no compactions are triggered.

We need some way to notice the fact that the ratio of deletes to rows is high and decide to compact those rowsets.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)