[HDFS-10867] [PROVIDED Phase 2] Block Bit Field Allocation of Provided Storage

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Later
• Component/s: hdfs
• Assignee: Unassigned
• Reporter: Ewan Higgs
• Created: 16/Sep/16 09:14
• Updated: 04/Nov/19 15:29
• Resolved: 04/Nov/19 15:29

Description

We wish to design and implement the following related features for provided storage:

1. Dynamic mounting of provided storage within a Namenode (mount, unmount)
2. Mount multiple provided storage systems on a single Namenode.
3. Support updates to the provided storage system without having to regenerate an fsimg.

A mount in the namespace addresses a corresponding set of block data. When unmounted, any block data associated with the mount becomes invalid and (eventually) unaddressable in HDFS. As with erasure-coded blocks, efficient unmounting requires that all blocks with that attribute be identifiable by the block management layer

In this subtask, we focus on changes and conventions to the block management layer. Namespace operations are covered in a separate subtask.

Issue Links

• relates to: HDFS-13350 Negative legacy block ID will confuse Erasure Coding to be considered as striped block
• relates to: HDFS-11382 Persist Erasure Coding Policy ID in a new optional field in INodeFile in FSImage