[
https://issues.apache.org/jira/browse/HDFS-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Radia updated HDFS-7240:
-------------------------------
Description:
[^HDFS Scalability-v2.pdf] describes areas where HDFS does well and its scaling
challenges and how to address those challenges. Scaling HDFS requires scaling
the namespace layer and also the block layer. _This jira provides a new block
layer, Hadoop Distributed Storage Layer (HDSL), that scales the block layer by
grouping blocks into containers thereby reducing the block-to-location map and
also reducing the number of block reports and their processing_
_A scalable namespace can be put on top this scalable block layer:_
* _HDFS-10419 describes how the existing NN can be modified to use the new
block layer._
* _HDFS-13074 also provides, as an_ *_interim_* _step; a scalable flat KV
namespace on top of the new block layer; while it does not provide the HDFS
API, it does support the Hadoop FS APIs (Hadoop FileSystem, FileContext)._
Old Description
This jira proposes to add object store capabilities into HDFS.
As part of the federation work (HDFS-1052) we separated block storage as a
generic storage layer. Using the Block Pool abstraction, new kinds of
namespaces can be built on top of the storage layer i.e. datanodes.
In this jira I will explore building an object store using the datanode
storage, but independent of namespace metadata.
I will soon update with a detailed design document.
was:
This jira proposes to add object store capabilities into HDFS.
As part of the federation work (HDFS-1052) we separated block storage as a
generic storage layer. Using the Block Pool abstraction, new kinds of
namespaces can be built on top of the storage layer i.e. datanodes.
In this jira I will explore building an object store using the datanode
storage, but independent of namespace metadata.
I will soon update with a detailed design document.
> Object store in HDFS
> --------------------
>
> Key: HDFS-7240
> URL: https://issues.apache.org/jira/browse/HDFS-7240
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Priority: Major
> Attachments: HDFS Scalability and Ozone.pdf, HDFS Scalability-v2.pdf,
> HDFS-7240.001.patch, HDFS-7240.002.patch, HDFS-7240.003.patch,
> HDFS-7240.003.patch, HDFS-7240.004.patch, HDFS-7240.005.patch,
> HDFS-7240.006.patch, HadoopStorageLayerSecurity.pdf, MeetingMinutes.pdf,
> Ozone-architecture-v1.pdf, Ozonedesignupdate.pdf, ozone_user_v0.pdf
>
>
> [^HDFS Scalability-v2.pdf] describes areas where HDFS does well and its
> scaling challenges and how to address those challenges. Scaling HDFS requires
> scaling the namespace layer and also the block layer. _This jira provides a
> new block layer, Hadoop Distributed Storage Layer (HDSL), that scales the
> block layer by grouping blocks into containers thereby reducing the
> block-to-location map and also reducing the number of block reports and their
> processing_
> _A scalable namespace can be put on top this scalable block layer:_
> * _HDFS-10419 describes how the existing NN can be modified to use the new
> block layer._
> * _HDFS-13074 also provides, as an_ *_interim_* _step; a scalable flat KV
> namespace on top of the new block layer; while it does not provide the HDFS
> API, it does support the Hadoop FS APIs (Hadoop FileSystem, FileContext)._
>
>
> Old Description
> This jira proposes to add object store capabilities into HDFS.
> As part of the federation work (HDFS-1052) we separated block storage as a
> generic storage layer. Using the Block Pool abstraction, new kinds of
> namespaces can be built on top of the storage layer i.e. datanodes.
> In this jira I will explore building an object store using the datanode
> storage, but independent of namespace metadata.
> I will soon update with a detailed design document.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
