[
https://issues.apache.org/jira/browse/HDFS-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-7170:
--------------------------------
Description:
DFSOutputStream creates the default policy suite locally to determine whether
the LAZY_PERSIST policy is set on a file so it can pass the appropriate flag to
DataNode via writeBlock. It should query the policies from the NameNode. Per
feedback from [~jingzhao] on HDFS-7159.
Additionally DFSOutputStream gets the effective policy on the file, it should
get the local storage policy since effective policy is subject to change. We
may need to extend HdfsFileStatus to expose it.
DFSClient will probably need to cache policies since we can't take the overhead
of an additional RPC call to NameNode per create/append.
was:
Per feedback from [~jingzhao] on HDFS-7159.
DFSOutputStream creates the default policy suite locally to determine whether
the LAZY_PERSIST policy is set on a file so it can pass the appropriate flag to
DataNode via writeBlock. It should query the policies from the NameNode.
DFSClient will probably need to cache policies since we can't take the overhead
of an additional RPC call to NameNode per create/append.
> DFSOutputStream should query policies from NameNode
> ---------------------------------------------------
>
> Key: HDFS-7170
> URL: https://issues.apache.org/jira/browse/HDFS-7170
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Affects Versions: HDFS-6581
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
>
> DFSOutputStream creates the default policy suite locally to determine whether
> the LAZY_PERSIST policy is set on a file so it can pass the appropriate flag
> to DataNode via writeBlock. It should query the policies from the NameNode.
> Per feedback from [~jingzhao] on HDFS-7159.
> Additionally DFSOutputStream gets the effective policy on the file, it should
> get the local storage policy since effective policy is subject to change. We
> may need to extend HdfsFileStatus to expose it.
> DFSClient will probably need to cache policies since we can't take the
> overhead of an additional RPC call to NameNode per create/append.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
