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-19165) TODO Handle stuck in transition: rit=OPENING, location=ve0538....
Date Thu, 02 Nov 2017 23:32:00 GMT

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

stack commented on HBASE-19165:

An operating hbase2 cluster keeps region state in meta. When an hbase2 comes up for the first
time, there is no 'state' entry for a region. Turns out we default OPENING. OPENING means
waiting for a callback which says either OPEN or FAILED. In this case the callback will never
trigger since callback an AMv2 thing. Let me figure another default, one that says this region
needs assigning.

> TODO Handle stuck in transition: rit=OPENING, location=ve0538....
> -----------------------------------------------------------------
>                 Key: HBASE-19165
>                 URL: https://issues.apache.org/jira/browse/HBASE-19165
>             Project: HBase
>          Issue Type: Bug
>          Components: migration
>            Reporter: stack
>            Priority: Critical
>             Fix For: 2.0.0-beta-1
> A few of us trying migration from hbase1 to hbase2 have run into various assignment issues.
In my case, I see that Master coming online, reading hbase:meta, finding an issue in OPENING
state and then just not assigning. My thought is that its expecting a callback to come in.
Eventually log is fills with this sort of stuff:
> 2017-11-02 15:02:54,237 WARN  [ProcExecTimeout] assignment.AssignmentManager: TODO Handle
stuck in transition: rit=OPENING, location=ve0528.halxg.cloudera.com,16020,1509657692581,
table=IntegrationTestBigLinkedList, region=919cc6636ffbed17f628f335d3a58726
> Let me get a cleaner run. This current log is polluted by a few restarts.

This message was sent by Atlassian JIRA

View raw message