hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4129) Memory limits of TaskTracker and Tasks should be in kiloBytes.
Date Tue, 09 Sep 2008 12:57:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vinod K V updated HADOOP-4129:

    Attachment: HADOOP-4129

Attaching a patch.
 - TestHighRAMJobs, TestProcfsBasedProcessTree and TestTaskMemoryManager all run successfully
 - Changed documentation to reflect the change to kilobytes.
 - For the sake of clarity, also mentioned that memory is in kilobytes in JobConf, TaskTracker
and TaskTrackerStatus.

> Memory limits of TaskTracker and Tasks should be in kiloBytes.
> --------------------------------------------------------------
>                 Key: HADOOP-4129
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4129
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>            Priority: Blocker
>         Attachments: HADOOP-4129
> HADOOP-3759 uses memory limits in kilo-bytes and HADOOP-3581 changed it to be in bytes.
Because of this, TestHighRAMJobs is failing on Linux. We should change this behaviour so that
all memory limits are considered to be in kilo-bytes.

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

View raw message