[
https://issues.apache.org/jira/browse/HADOOP-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651510#action_12651510
]
Hemanth Yamijala commented on HADOOP-4513:
------------------------------------------
I also ran contrib tests on my box, and they all passed. As the patch only
touches the capacity scheduler and no classes in core, I am not running core
tests. Will commit this patch now, as the patch queue is quite long, and there
are some important patches waiting on this one for merging (for e.g.
HADOOP-4035)
> 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.
