You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2018/08/01 06:24:28 UTC
[jira] [Issue Comment Deleted] (HBASE-19165) TODO Handle stuck in
transition: rit=OPENING, location=ve0538....
[ https://issues.apache.org/jira/browse/HBASE-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated HBASE-19165:
--------------------------
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> 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, 2.0.0
>
> Attachments: HBASE-19165.master.001.patch, HBASE-19165.master.002.patch, HBASE-19165.master.003.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
(v7.6.3#76005)