[
https://issues.apache.org/jira/browse/HBASE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905086#action_12905086
]
Jonathan Gray commented on HBASE-2949:
--------------------------------------
New ExecutorService and EventHandlers from master rewrite provide a mechanism
to execute as async (in an executor service thread pool) or sync (in the
callers thread).
Other jiras like HBASE-2832, HBASE-1476, and HBASE-2375 will deal with moving
flush/split/compact into handlers. Once that is done, it would be trivial to
make the calls synchronous. However the naive implementation would hold the
RPC open the whole time. We may want to make the request async but then have
another call to check, as stack says above.
There's been discussion about adding status into ZK about what RSs and masters
are doing (compactions, log splitting, etc). Maybe we could use that mechanism?
As far as progress, that would require bigger changes to flush/compact code but
would definitely be something to think about while re-implementing them in
handlers.
I think for first cut, let's not worry about canceling or progress, just a
single blocking call would be significantly better than what we have available
today.
> Add synchronous compact/split/flush or add a callback that gets pulled when
> compact/split/flush completes (and a progressable on how much is done)
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-2949
> URL: https://issues.apache.org/jira/browse/HBASE-2949
> Project: HBase
> Issue Type: New Feature
> Reporter: stack
>
> Users have asked for this w/ a while. They start a major compaction and are
> a little baffled when the shell returns immediately. We need to make the
> call synchronous or add a callback or provide a progressable so user can see
> how complete the task is. Should we include a cancel task? "Hey! Why did
> everything go slow of a sudden?" .... 5 minutes later "A major compaction
> started on hbase... how do we turn it off?"
> The need for this feature was also mentioned in HBASE-2701
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
