[
https://issues.apache.org/jira/browse/HADOOP-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-4035:
-------------------------------------
Description: HADOOP-3759 introduced configuration variables that can be
used to specify memory requirements for jobs, and also modified the
tasktrackers to report their free memory. The capacity scheduler in HADOOP-3445
should schedule tasks based on these parameters. A task that is scheduled on a
TT that uses more than the default amount of memory per slot can be viewed as
effectively using more than one slot, as it would decrease the amount of free
memory on the TT by more than the default amount while it runs. The scheduler
should make the used capacity account for this additional usage while enforcing
limits, etc. (was: HADOOP-3749 introduced configuration variables that can be
used to specify memory requirements for jobs, and also modified the
tasktrackers to report their free memory. The capacity scheduler in HADOOP-3445
should schedule tasks based on these parameters. A task that is scheduled on a
TT that uses more than the default amount of memory per slot can be viewed as
effectively using more than one slot, as it would decrease the amount of free
memory on the TT by more than the default amount while it runs. The scheduler
should make the used capacity account for this additional usage while enforcing
limits, etc.)
Corrected typo in description on JIRA number.
> Modify the capacity scheduler (HADOOP-3445) to schedule tasks based on memory
> requirements and task trackers free memory
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4035
> URL: https://issues.apache.org/jira/browse/HADOOP-4035
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Vivek Ratan
> Fix For: 0.19.0
>
>
> HADOOP-3759 introduced configuration variables that can be used to specify
> memory requirements for jobs, and also modified the tasktrackers to report
> their free memory. The capacity scheduler in HADOOP-3445 should schedule
> tasks based on these parameters. A task that is scheduled on a TT that uses
> more than the default amount of memory per slot can be viewed as effectively
> using more than one slot, as it would decrease the amount of free memory on
> the TT by more than the default amount while it runs. The scheduler should
> make the used capacity account for this additional usage while enforcing
> limits, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
