[
https://issues.apache.org/jira/browse/HDFS-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341735#comment-16341735
]
Jitendra Nath Pandey commented on HDFS-7240:
--------------------------------------------
[~owen.omalley], that's a great suggestion. I agree it is better to track the
key value namespace work in a separate jira, while this jira focusses on the
new storage layer.
Hadoop Storage Layer is a good suggestion, I would suggest a slight
modification to call it Hadoop Distributed Storage Layer (HDSL).
It is important to keep the storage layer separate and independent of the
namespace implementation, as multiple different namespaces can be built on top
of HDSL. For example, HDFS-10419 implements a hierarchical namespace/NN on this
storage layer.
I will create a separate jira for ozone's KV namespace.
> 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-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
>
>
> 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]
