hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7212) Globally Barriered Procedure mechanism
Date Fri, 28 Dec 2012 22:34:12 GMT

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

Hadoop QA commented on HBASE-7212:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12562609/pre-hbase-7212.v8.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 78 new or modified
tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3741//console

This message is automatically generated.
                
> Globally Barriered Procedure mechanism
> --------------------------------------
>
>                 Key: HBASE-7212
>                 URL: https://issues.apache.org/jira/browse/HBASE-7212
>             Project: HBase
>          Issue Type: Sub-task
>          Components: snapshots
>    Affects Versions: hbase-6055
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>             Fix For: hbase-6055
>
>         Attachments: 121127-global-barrier-proc.pdf, hbase-7212.patch, hbase-7212.v5.patch,
hbase-7212.v8.patch, pre-hbase-7212.patch, pre-hbase-7212.v5.patch, pre-hbase-7212.v8.patch
>
>
> This is a simplified version of what was proposed in HBASE-6573.  Instead of claiming
to be a 2pc or 3pc implementation (which implies logging at each actor, and recovery operations)
this is just provides a best effort global barrier mechanism called a Procedure.  
> Users need only to implement a methods to acquireBarrier, to act when insideBarrier,
and to releaseBarrier that use the ExternalException cooperative error checking mechanism.
> Globally consistent snapshots require the ability to quiesce writes to a set of region
servers before a the snapshot operation is executed.  Also if any node fails, it needs to
be able to notify them so that they abort.
> The first cut of other online snapshots don't need the fully barrier but may still use
this for its error propagation mechanisms.
> This version removes the extra layer incurred in the previous implementation due to the
use of generics, separates the coordinator and members, and reduces the amount of inheritance
used in favor of composition.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message