[
https://issues.apache.org/jira/browse/HDFS-10867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewan Higgs resolved HDFS-10867.
-------------------------------
Resolution: Later
This work will be done in a future ticket when we handle bidirectional stores
(where the external store can create new files and have them show up in HDFS).
> [PROVIDED Phase 2] Block Bit Field Allocation of Provided Storage
> -----------------------------------------------------------------
>
> Key: HDFS-10867
> URL: https://issues.apache.org/jira/browse/HDFS-10867
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs
> Reporter: Ewan Higgs
> Priority: Major
> Attachments: Block Bit Field Allocation of Provided Storage.pdf
>
>
> We wish to design and implement the following related features for provided
> storage:
> # Dynamic mounting of provided storage within a Namenode (mount, unmount)
> # Mount multiple provided storage systems on a single Namenode.
> # 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
