[
https://issues.apache.org/jira/browse/HDFS-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217441#comment-15217441
]
Chris Nauroth commented on HDFS-8210:
-------------------------------------
[~anu], thank you again.
bq. Would you have an error entry in the return set or would the whole query
fail ?
My initial thinking had been to fail the whole query, under the assumption that
the inputs could be pre-validated before passing to SCM if more granular error
reporting was needed. If this turns out to be cumbersome in practice though,
we definitely could add an error code to the individual {{LocatedContainer}}
responses.
bq. when we actually have prefix lookups we might want to add some test cases
that actually return different values for prefix and key strings.
Yes, this testing definitely will become important as the logic for determining
locations evolves.
> 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)
