[
https://issues.apache.org/jira/browse/HBASE-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239915#comment-16239915
]
stack commented on HBASE-19165:
-------------------------------
bq. Does it make sense to return OFFLINE state itself from here rather than
null and handle the null in other place?
This was my first attempt. My fear is ruling that an empty state column means
OFFLINE. I think if state column is empty, then its a migration or a problem in
meta. If either, I was thinking we need to do some probing to figure which it
is... asking RegionServers what they have. Doing this inside in the
RegionStateStore context seems the wrong place. Need to back out into the
AssignmentManager where we have more context.
The test failure is interesting. It is a dependency on old state of OPENING.
Trying to track it down.
Thanks for review [~anoop.hbase]
> 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
>
>
> 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)
