[HBASE-698] HLog recovery is not performed after master failure

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.1.2, 0.2.1, 0.19.3
• Fix Version/s: 0.20.0
• Component/s: master, regionserver
• Hadoop Flags: Reviewed
• Release Note: Old setups running 0.19 should first delete everything that's log_* in HBase root HDFS folder before updating. Make sure HBase is down before doing that. Also this will be done by migration in 0.20.0
• Assignee: Jean-Daniel Cryans
• Reporter: Clint Morgan
• Created: 19/Jun/08 00:36
• Updated: 21/Jan/11 05:38
• Resolved: 14/Jul/09 16:49

Description

I have a local cluster running, and its logging to
<hbase>/log_X.X.X.X_1213228101021_60020/

Then I kill both master and regionserver, and restart. Looking through
the logs I don't see anything about trying to recover from this hlog,
it just creates a new hlog alongside the existing one (with a new
startcode). The older hlog seems to be ignored, and the tables
created in the inital session are all gone.

Issue Links

• is blocked by: HBASE-728 Supporting for HLog appends
• is blocked by: HBASE-546 Use Zookeeper in HBase
• is blocked by: HBASE-1302 When a new master comes up, regionservers should continue with their region assignments from the last master