hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Stepachev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11689) Track meta in transition
Date Thu, 14 Aug 2014 08:08:12 GMT

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

Andrey Stepachev commented on HBASE-11689:

Researched how it implemented now.
We have a couple of options to do this task:

# We can, as proposed in comments above, enhance MetaRegionServer with additional 
_optional_ field typed RegionState.State. But that solution has implications:
#* we need to combat with possibly concurrent updates (RS and Master, both write to that znode)
#* RS has to know what state to write into updated PB (read and versioned update, I suppose).

# We can create new znode or hierarchy of znodes and store state for each meta region (only
for one currently)
and can restrict PB to have all fields _required_.

I'd prefer to go with second solution, it is more cosine and provides good visibility and
write paths (only Master writes
to state and only RS writes to location znode).

What do you think about that. Or there is another, better solution exists?

> Track meta in transition
> ------------------------
>                 Key: HBASE-11689
>                 URL: https://issues.apache.org/jira/browse/HBASE-11689
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>            Reporter: Jimmy Xiang
>            Assignee: Andrey Stepachev
> With ZK-less region assignment, user regions in transition are tracked in meta. We need
a way to track meta in transition too.

This message was sent by Atlassian JIRA

View raw message