[
https://issues.apache.org/jira/browse/HBASE-18905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185322#comment-16185322
]
Duo Zhang commented on HBASE-18905:
-----------------------------------
Because compaction is per Store...
If you requestCompaction on a Region, it may lead to multiple compaction tasks
if the Region has multiple Stores.
But anyway, I think there maybe a problem that a requestCompaction could fail,
for example, if there is no files in the given Store. I do not know how user
could know this information, maybe through the RegionObserver.preXXX? Need to
confirm.
> Allow CPs to request flush/compaction on Region
> -----------------------------------------------
>
> Key: HBASE-18905
> URL: https://issues.apache.org/jira/browse/HBASE-18905
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 2.0.0-alpha-4
>
>
> Follow up for HBASE-18183
> As per that Jira, we keep only requestCompaction API in Region. We did not
> have any such for flush in Region. Only API which was there is a flush which
> will block the callee unless flush is done. This issue has to tacke
> 1. Decide whether we need a requestFlush in Region and if so add
> 2. Whether the requestCompaction (And requestFlush too) should return a
> Future? Right now the former do not return any but allow to pass a
> CompactionLifeCycleTracker which will get notified on start and end of
> compaction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
