You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2009/05/29 07:38:45 UTC

[jira] Commented: (HADOOP-5932) MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker

    [ https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714304#action_12714304 ] 

Hemanth Yamijala commented on HADOOP-5932:
------------------------------------------

+1 for the fix. There are comments I stumbled upon independently in the test cases which I've already raised in HADOOP-5934. So, I am not repeating those here under the assumption these will be fixed there.

Can you please upload the results of test-patch and capacity scheduler tests ?
Also, can you please make sure there's a patch that works for the 20 branch ?

> MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5932
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5932
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 0.20.0
>            Reporter: Karam Singh
>         Attachments: HADOOP-5932-20090528.1.txt, HADOOP-5932-20090528.txt
>
>
> MemoryMatcher logs 0 as freeMemOnTT even though there are free slots available on TaskTraker

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.