[
https://issues.apache.org/jira/browse/HBASE-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-1117:
----------------------------------
Priority: Major (was: Blocker)
Fix Version/s: (was: 0.19.0)
Summary: Failed region assignments on startup after Hadoop upgrade
(was: Region assignment on startup is broken)
It was just luck that the cluster came up before (twice). I'm seeing this again
on r732908, even on r723491, which is before the big set of master changes that
Jim committed. Sorry to incorrectly report blame. Is something new. Could be
legacy data issue. I did not have any problems with HBase TRUNK until I
upgraded Hadoop. I'm going to move the old data out of the way and start a new
experiment to see if this happens again.
> Failed region assignments on startup after Hadoop upgrade
> ---------------------------------------------------------
>
> Key: HBASE-1117
> URL: https://issues.apache.org/jira/browse/HBASE-1117
> Project: Hadoop HBase
> Issue Type: Bug
> Environment: apurtell cluster, HBase TRUNK on Hadoop 0.19.1-dev
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Attachments: hbase-hadoop-wtp.back.cluster.HMaster-sjdc-atr-dc-2.log,
> hbase-hadoop-wtp.back.cluster.HMaster-sjdc-atr-dc-2.log
>
>
> I can't get my cluster all the way up after upgrading to Hadoop 0.19. Master
> is ignoring MSG_REPORT_PROCESS_OPEN from various regionservers, skipping
> regions it thinks are in transition. Master UI is also unresponsive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
