hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sreekanth Ramakrishnan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4513) Capacity scheduler should initialize tasks asynchronously
Date Tue, 18 Nov 2008 04:01:44 GMT

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

Sreekanth Ramakrishnan updated HADOOP-4513:
-------------------------------------------

    Attachment: HADOOP-4513-2.patch

Attaching new patch by changing booleans to volatile, in order to address JMM issues as mentioned
in JIRA [HADOOP-4671|https://issues.apache.org/jira/browse/HADOOP-4671]

> Capacity scheduler should initialize tasks asynchronously
> ---------------------------------------------------------
>
>                 Key: HADOOP-4513
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4513
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 0.19.0
>            Reporter: Hemanth Yamijala
>            Assignee: Sreekanth Ramakrishnan
>             Fix For: 0.19.1
>
>         Attachments: HADOOP-4513-1.patch, HADOOP-4513-2.patch
>
>
> Currently, the capacity scheduler initializes tasks on demand, as opposed to the eager
initialization technique used by the default scheduler. This is done in order to save JT memory
footprint. However, the initialization is done in the {{assignTasks}} API which is not a good
idea as task initialization could be a time consuming operation. This JIRA is to move out
the initialization outside the {{assignTasks}} API and do it asynchronously.

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


Mime
View raw message