hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6199) Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING
Date Mon, 11 Jun 2012 20:02:42 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-6199:

    Attachment: 6199v4.txt

Cleaner version (the v3 didn't apply to fresh trunk)
> Change PENDING_OPEN scope from pre-rpc open to OPENING to just post-rpc open to OPENING
> ---------------------------------------------------------------------------------------
>                 Key: HBASE-6199
>                 URL: https://issues.apache.org/jira/browse/HBASE-6199
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: stack
>         Attachments: 6199v4.txt, pending_open.txt, pending_open2.txt, pending_open3.txt
> PENDING_OPEN currently is a murky state.  Its a master in-memory state with no corresponding
znode state that sits between OFFLINE and OPENING states.
> The OFFLINE state is set by the master when it goes to open a region.  OPENING is set
by the regionserver after its assumed control of a region and is moving it through the OPENING
process.  PENDING_OPEN currently spans the open rpc invocation.  This state is in place pre-open-rpc-invocation,
during open-rpc-invocation, and post-rpc-invocation until we get the OPENING callback. That
PENDING_OPEN covers this many different conditions effectively makes it unactionable.
> This issue proposes PENDING_OPEN only be in place post-rpc-invocation.  Now its meaning
is clear as the space between rpc-open-invocation and our receiving the callback which sets
RegionState to OPENING.  PENDING_OPEN becomes actionable too in that if a regionserver dies
post rpc-open-invocation, we know that we can reassign the region.
> See https://issues.apache.org/jira/browse/HBASE-6060?focusedCommentId=13292646&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13292646
for more discussion.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message