[
https://issues.apache.org/jira/browse/HDFS-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740200#comment-13740200
]
Andrew Wang commented on HDFS-5051:
-----------------------------------
Gotcha, makes sense. I definitely only wanted to address caching finalized
blocks at first, but I was thinking about the case where an
"append+write+close" would lead to a finalized block with a new longer length.
Let's punt that out to an "auto-caching" subtask (will file).
So, I'll remove the gen stamp and length in HDFS-5092; will edit it with this
and the other todo items.
> Propagate cache status information from the DataNode to the NameNode
> --------------------------------------------------------------------
>
> Key: HDFS-5051
> URL: https://issues.apache.org/jira/browse/HDFS-5051
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Reporter: Colin Patrick McCabe
> Assignee: Andrew Wang
> Attachments: hdfs-5051-1.patch, hdfs-5051-2.patch
>
>
> The DataNode needs to inform the NameNode of its current cache state. Let's
> wire up the RPCs and stub out the relevant methods on the DN and NN side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
