[
https://issues.apache.org/jira/browse/HADOOP-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod K V updated HADOOP-5932:
------------------------------
Attachment: HADOOP-5932-20090528.txt
Discussed with Karam regarding this and looked at the logs. The bug happened
due to a misplaced local variable myVmem initialization in
MemoryMatcher.getMemReservedForTasks().
Quick patch for testing.
> 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.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.
