[
https://issues.apache.org/jira/browse/HADOOP-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-4513:
-------------------------------------
Attachment: HADOOP-4513-8.patch
The test cases in the earlier patch were too complex and too non-deterministic
given the asynchronous nature of the patch. So Sreekanth and I refactored the
code to enable better testing, and modified the test cases to be run in a
synchronous and deterministic fashion. We are also not dependent on any sleep
calls. I updated the documentation on the patch quite a bit.
> 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,
> HADOOP-4513-3.patch, HADOOP-4513-4.patch, HADOOP-4513-5-NOBUSYWAITING.patch,
> HADOOP-4513-6.patch, HADOOP-4513-8.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.
