Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
This was observed while doing HBase WAL recovery. HBase uses append to write to its write ahead log. So initially the pipeline is setup as
DN1 --> DN2 --> DN3
This WAL needs to be read when DN1 fails since it houses the HBase regionserver for the WAL.
HBase first recovers the lease on the WAL file. During recovery, we choose DN1 as the primary DN to do the recovery even though DN1 has failed and is not heartbeating any more.
To speedup lease/block recovery, we always choose the datanode with the most recent heartbeat.
Attachments
Issue Links
- relates to
-
HDFS-4721 Speed up lease/block recovery when DN fails and a block goes into recovery
- Closed