[
https://issues.apache.org/jira/browse/HDFS-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217434#comment-15217434
]
Anu Engineer commented on HDFS-8210:
------------------------------------
[~cnauroth] Thanks for updating the patch. +1, pending jenkins.
Some minor comments / questions for future.
# As a corner case, what happens if a request for a invalid key is made to SCM
? For example, an invalid volume name or path. How do we propose to handle
that, Would you have an error entry in the return set or would the whole
query fail ? Feel free to define the semantics of this in later patches.
# Again a suggestion for future, when we actually have prefix lookups we might
want to add some test cases that actually return different values for prefix
and key strings.
> Ozone: Implement storage container manager
> -------------------------------------------
>
> Key: HDFS-8210
> URL: https://issues.apache.org/jira/browse/HDFS-8210
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Jitendra Nath Pandey
> Assignee: Chris Nauroth
> Attachments: HDFS-8210-HDFS-7240.006.patch,
> HDFS-8210-HDFS-7240.007.patch, HDFS-8210-HDFS-7240.1.patch,
> HDFS-8210-HDFS-7240.2.patch, HDFS-8210-HDFS-7240.3.patch,
> HDFS-8210-HDFS-7240.4.patch, HDFS-8210-HDFS-7240.5.patch
>
>
> The storage container manager collects datanode heartbeats, manages
> replication and exposes API to lookup containers. This jira implements
> storage container manager by re-using the block manager implementation in
> namenode. This jira provides initial implementation that works with
> datanodes. The additional protocols will be added in subsequent jiras.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
