You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2013/10/21 21:31:45 UTC
[jira] [Resolved] (HDFS-5378) In CacheReport, don't send genstamp
and length on the wire
[ https://issues.apache.org/jira/browse/HDFS-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin Patrick McCabe resolved HDFS-5378.
----------------------------------------
Resolution: Fixed
Fix Version/s: HDFS-4949
> In CacheReport, don't send genstamp and length on the wire
> ----------------------------------------------------------
>
> Key: HDFS-5378
> URL: https://issues.apache.org/jira/browse/HDFS-5378
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode
> Affects Versions: HDFS-4949
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Fix For: HDFS-4949
>
> Attachments: HDFS-5378-caching.001.patch, HDFS-5378-caching.002.patch, HDFS-5378-caching.003.patch, HDFS-5378-caching.004.patch
>
>
> As discussed in HDFS-5096, we don't need genstamp and block length when processing cache reports. So let's not send them over the wire (it increases the size of cache reports to 3x what it could be).
> Also, we should report the caching statistics alongside the normal DN stats in {{StorageReport}}. There's no reason for them to be separate. Since the new fields will be optional and default to 0, there will be no extra overhead in the non-caching case.
--
This message was sent by Atlassian JIRA
(v6.1#6144)