hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16786) Procedure V2 - Move ZK-lock's uses to Procedure framework locks (LockProcedure)
Date Wed, 25 Jan 2017 17:34:26 GMT

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

stack commented on HBASE-16786:

[~syuanjiang] Nod. Makes sense. Lets see.

You've seen this: https://github.com/matteobertozzi/hbase/commit/dff1606f488a2bf160afdd81c47f72ead5d5e172

It is split embracing AMv2 and Pv2 spawning subprocedures to do steps. Our current, redone
split procedure seems a mapping of the current split model migrating stuff like PONR, concepts
we should be able to do without when up on the new AM. We need to do whats in dff1606f488a2bf160afdd81c47f72ead5d5e172
for split? And I'd imagine merge would change similar?

> Procedure V2 - Move ZK-lock's uses to Procedure framework locks (LockProcedure)
> -------------------------------------------------------------------------------
>                 Key: HBASE-16786
>                 URL: https://issues.apache.org/jira/browse/HBASE-16786
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Appy
>            Assignee: Matteo Bertozzi
>             Fix For: 2.0.0
>         Attachments: HBASE-16786.master.001.patch, HBASE-16786.master.002.patch, HBASE-16786.master.003.patch,
HBASE-16786.master.004.patch, HBASE-16786.master.005.patch, HBASE-16786.master.006.patch,
HBASE-16786.master.007.patch, HBASE-16786.master.008.patch, HBASE-16786.master.009.patch,
HBASE-16786.master.010.patch, HBASE-16786.master.011.patch, HBASE-16786.master.012.patch,

This message was sent by Atlassian JIRA

View raw message