Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 9 Oct 2013 23:10:42 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12666370.1377888998405.41794.1381360242521@arcas>
In-Reply-To: <JIRA.12666370.1377888998405@arcas>
References: <JIRA.12666370.1377888998405@arcas>
Subject: [jira] [Commented] (HDFS-5149) Support for federated cache pools
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790973#comment-13790973 ] 

Andrew Wang commented on HDFS-5149:
-----------------------------------

Hey Chris, great to hear that things look good. This was more of a tracking JIRA than anything else, I had a vague notion that we might need to fix cacheReports on the DN, but it seems like we're good.

We can just close it out if you like, or if you have time to do some testing to see how things behave, that'd be much appreciated too.

> Support for federated cache pools
> ---------------------------------
>
>                 Key: HDFS-5149
>                 URL: https://issues.apache.org/jira/browse/HDFS-5149
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>    Affects Versions: HDFS-4949
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>
> The federation concept of a "blockpool" has not pervaded the caching implementation thus far, e.g. datanodes do not track and report usage by block pool, some namenode operations are not block pool aware. This requires re-examination of protobufs / protocol / handling throughout.


--
This message was sent by Atlassian JIRA
(v6.1#6144)