[
https://issues.apache.org/jira/browse/HDFS-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738949#comment-13738949
]
Colin Patrick McCabe commented on HDFS-5051:
--------------------------------------------
bq. Nit: Document the \@return DatanodeProtocol#cacheReport. Nit: "used to
communicated blocks" -> "used to communicate blocks"
This JIRA is already committed (it's marked as "fixed"). Let's do this in
HDFS-5053. I have pasted the comments there so we won't forget.
bq. In cache report, do we need to have block length and generation stamp or
just the block ID suffices?
Let's address this later in HDFS-5053.
bq. Should we send cache report only if some thing in the cache changes,
instead of blindly every 10 seconds? This could happen in a later patch/jira.
We filed HDFS-5092 for this.
> 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
