You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/11/06 22:17:34 UTC

[jira] [Commented] (HBASE-10544) Surface completion state of global administrative actions

    [ https://issues.apache.org/jira/browse/HBASE-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200949#comment-14200949 ] 

Andrew Purtell commented on HBASE-10544:
----------------------------------------

Just to tie in related discussion elsewhere.

If we implemented something like Accumulo's FATE and had the master use that when creating, modifying, enabling/disabling tables, then a client could track the completion state of the master's work that way. See HBASE-5459

We'd still need an answer to track distributed admin actions like compaction and flush requests, probably with a Procedure. 

> Surface completion state of global administrative actions
> ---------------------------------------------------------
>
>                 Key: HBASE-10544
>                 URL: https://issues.apache.org/jira/browse/HBASE-10544
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>             Fix For: 0.99.2
>
>
> When issuing requests for global administrative actions, such as major compaction, users have to look for indirect evidence the action has completed, and cannot really be sure of the final state. 
> Hat tip to [~jdcryans] and [~stack].
> We can approach this a couple of ways. We could add a per regionserver metric for percentage of admin requests complete, maybe also aggregated by the master. This would provide a single point of reference. However if we also want to insure 100% completion even in the presence of node failures, or provide separate completion feedback for each request, I think we need to redo flush and compaction requests as Procedures. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)