hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6573) Distributed Three-Phase Commit framework.
Date Sat, 01 Sep 2012 19:09:07 GMT

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

Jesse Yates commented on HBASE-6573:

Switching this to be a Three-Phase (rather than Two-Phase) commit and making it a framework
for orchestrating distributed commits. After Jon's comments and talking with Lars H. about
what would be nice to have pulled out of snapshots, it made more sense to abstract out the
entire control mechanism into the general process with interfaces for additional orchestration
(currently just ZooKeeper, but could easily be done with RPC too) and abstract worker-side
(cohort) processing it comes out to be a pretty clean abstraction. The downside means rewriting
a bit of the snapshot stuff, but that should results in at least a page if not more less for
review on that (HBASE-6055). 

So anyways, new review is up, still at https://reviews.apache.org/r/6592/
> Distributed Three-Phase Commit framework.
> -----------------------------------------
>                 Key: HBASE-6573
>                 URL: https://issues.apache.org/jira/browse/HBASE-6573
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 0.96.0
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.96.0
>         Attachments: java_HBASE-6573-v0.patch
> For HBASE-6055 (snapshots), we do two-phase commit in several places. This is a generally
useful paradigm for a distributed system.

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

View raw message