[ https://issues.apache.org/jira/browse/HBASE-18906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222234#comment-16222234 ]
Hudson commented on HBASE-18906: -------------------------------- FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3954 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3954/]) HBASE-18906 Provide Region#waitForFlushes API. (anoopsamjohn: rev 15b32460f9484fc0c635172c81b6a6315283775a) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > Provide Region#waitForFlushes API > --------------------------------- > > 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 > Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18906.patch, HBASE-18906_V2.patch, > HBASE-18906_V2.patch > > > Expose an API for the CPs to wait for all on going flushes in a Region. The > API should support taking a time out. > Background > 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)