[
https://issues.apache.org/jira/browse/HBASE-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858030#action_12858030
]
Kannan Muthukkaruppan commented on HBASE-2453:
----------------------------------------------
Not totally convinced about this. If your workload is IO bound, processing the
deletes more aggressively (i.e. during minor compactions) even if it meant some
extra CPU might be good overall.
Can we atleast make this a configurable option? We should do some numbers to
see what the savings of not doing delete processing are.
> Revisit compaction policies after HBASE-2248 commit
> ---------------------------------------------------
>
> Key: HBASE-2453
> URL: https://issues.apache.org/jira/browse/HBASE-2453
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Priority: Critical
> Fix For: 0.20.4, 0.20.5, 0.21.0
>
> Attachments: HBASE-2453-v1.patch
>
>
> HBASE-2248 turned Gets into Scans server-side. It also removed the invariant
> that deletes in a file only apply to other files and not itself (no longer
> processes MemStore deletes when the delete happens). This has implications
> for our minor compaction policy.
> We are currently processing deletes during minor compactions in a way that
> makes it so we do the actual deleting as we compact, but we retain the delete
> records themselves. This makes it so we retain the invariant of deletes only
> applying to other files.
> Since this is now gone post HBASE-2248, we should revisit our compaction
> policies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
