[
https://issues.apache.org/jira/browse/HDFS-8669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-8669:
----------------------------
Description: Currently DFSStripedInputStream assumes we always have
complete internal block location information, i.e., we can always get all the
DataNodes for a striped block group. In a lot of scenarios the client cannot
get complete block location info, e.g., some internal blocks are missing and
the NameNode has not finished the recovery yet. We should add functionality to
handle missing block locations in DFSStripedInputStream. (was: Currently
DFSStripedInputStream assumes we always have complete internal block location
information, i.e., we can always get all the DataNodes for a striped block
group. We should add functionality to handle missing block locations.)
> Erasure Coding: handle missing internal block locations in
> DFSStripedInputStream
> --------------------------------------------------------------------------------
>
> Key: HDFS-8669
> URL: https://issues.apache.org/jira/browse/HDFS-8669
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Jing Zhao
> Assignee: Jing Zhao
>
> Currently DFSStripedInputStream assumes we always have complete internal
> block location information, i.e., we can always get all the DataNodes for a
> striped block group. In a lot of scenarios the client cannot get complete
> block location info, e.g., some internal blocks are missing and the NameNode
> has not finished the recovery yet. We should add functionality to handle
> missing block locations in DFSStripedInputStream.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
