[ https://issues.apache.org/jira/browse/HBASE-18906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209046#comment-16209046 ]
Duo Zhang commented on HBASE-18906: ----------------------------------- I have uploaded a patch in HBASE-18989 where I added more methods in CompactionLifeCycleTracker for better tracking the completion of a compaction request. I think we can do the same for flush. Use a tracker instead of returning a CompletableFuture is that, we will also pass the tracker to the CP hooks so you can carry some information on the track and pass them to the hooks. Thanks. > Investigate Phoenix usages of Region#waitForXXX APIs > ---------------------------------------------------- > > Key: HBASE-18906 > URL: https://issues.apache.org/jira/browse/HBASE-18906 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors > Reporter: Anoop Sam John > Assignee: Anoop Sam John > Fix For: 2.0.0-alpha-4 > > > While reviewing HBASE-18183, Andy pointed out that Phoenix uses > waitForFlushesAndCompactions and/or waitForFlushes for diff reasons. This > issue is to see why they need them and whether alternate ways are possible. > This seems to be too much internal stuff and a normal CP hook calling these > would be dangerous. > If there are alternate ways for Phoenix not to use this and not landing in > issues (As said by Andy) we should suggest/fix for them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)