[
https://issues.apache.org/jira/browse/HBASE-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244904#comment-16244904
]
stack commented on HBASE-19165:
-------------------------------
I had the scenario wrong. After study, I see that the region state field in
hbase:meta can also be empty when we restore a table from a snapshot. Previous
regions were hard-coded in the OPENING state. Now they are not given any state.
The RestoreSnapshotProcedure was doing a get of all Regions in the table but
was only getting back 'online' -- i.e. non-OFFLINE -- regions so it was never
doing the online.
.002 has RestoreSnapshotProcedure query for both online and offline regions
when it goes to enable the restored table.
> 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
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19165.master.001.patch,
> HBASE-19165.master.002.patch, HBASE-19165.master.003.patch
>
>
> 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
(v6.4.14#64029)
