Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 24 May 2016 01:44:12 +0000 (UTC)
From: "Yiqun Lin (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12971930.1463972054000.272661.1464054252874@Atlassian.JIRA>
In-Reply-To: <JIRA.12971930.1463972054000@Atlassian.JIRA>
References: <JIRA.12971930.1463972054000@Atlassian.JIRA> <JIRA.12971930.1463972054440@arcas>
Subject: [jira] [Commented] (HDFS-10448) CacheManager#checkLimit  always
 assumes a replication factor of 1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 24 May 2016 01:44:14 -0000


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

Yiqun Lin commented on HDFS-10448:
----------------------------------

So, [~cmccabe], what do you think the patch for this?

> CacheManager#checkLimit  always assumes a replication factor of 1
> -----------------------------------------------------------------
>
>                 Key: HDFS-10448
>                 URL: https://issues.apache.org/jira/browse/HDFS-10448
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: caching
>    Affects Versions: 2.7.1
>            Reporter: Yiqun Lin
>            Assignee: Yiqun Lin
>         Attachments: HDFS-10448.001.patch
>
>
> The logic in {{CacheManager#checkLimit}} is not correct. In this method, it does with these three logic:
> First, it will compute needed bytes for the specific path.
> {code}
> CacheDirectiveStats stats = computeNeeded(path, replication);
> {code}
> But the param {{replication}} is not used here. And the bytesNeeded is just one replication's vaue.
> {code}
> return new CacheDirectiveStats.Builder()
>         .setBytesNeeded(requestedBytes)
>         .setFilesCached(requestedFiles)
>         .build();
> {code}
> Second, then it should be multiply by the replication to compare the limit size because the method {{computeNeeded}} was not used replication.
> {code}
> pool.getBytesNeeded() + (stats.getBytesNeeded() * replication) > pool.getLimit()
> {code}
> Third, if we find the size was more than the limit value and then print warning info. It divided by replication here, while the {{stats.getBytesNeeded()}} was just one replication value.
> {code}
>       throw new InvalidRequestException("Caching path " + path + " of size "
>           + stats.getBytesNeeded() / replication + " bytes at replication "
>           + replication + " would exceed pool " + pool.getPoolName()
>           + "'s remaining capacity of "
>           + (pool.getLimit() - pool.getBytesNeeded()) + " bytes.");
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org