[
https://issues.apache.org/jira/browse/HADOOP-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521525
]
Jim Kellerman commented on HADOOP-1527:
---------------------------------------
Even better, if the master discovers a stale entry in the root or meta regions,
it should go look to see if the log file exists an split it before assigning
the region to a new server.
This would even handle the case where the region server serving the root region
died because it is highly unlikely that a region server would have only been
serving the root region.
So the plan of attack is to add a check in the master upon discovery of a stale
entry in the root and meta regions, and to create a separate utility to recover
a region server log in the unlikely event that a region server was only serving
the root region.
> Region server won't start because logdir exists
> -----------------------------------------------
>
> Key: HADOOP-1527
> URL: https://issues.apache.org/jira/browse/HADOOP-1527
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: Jim Kellerman
>
> Starting and then impolitely stopping a cluster I came across the following:
> 2007-06-25 19:43:31,449 ERROR org.apache.hadoop.hbase.HRegionServer: Can not
> start region server because
> org.apache.hadoop.hbase.RegionServerRunningException: region server already
> running at 208.76.44.140:60010 because logdir exists
> at
> org.apache.hadoop.hbase.HRegionServer.<init>(HRegionServer.java:447)
> at
> org.apache.hadoop.hbase.HRegionServer.<init>(HRegionServer.java:372)
> at org.apache.hadoop.hbase.HRegionServer.main(HRegionServer.java:1233)
> Region server should recover or offer a recovery path when we run into this
> condition.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
