[
https://issues.apache.org/jira/browse/HADOOP-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665406#action_12665406
]
Sreekanth Ramakrishnan commented on HADOOP-5068:
------------------------------------------------
Looked at the attached patch. The patch looks good.
But can we do one of the below:
* Change the initialization poller interval in FakeResourceManagerConf same way
reclaim capacity interval is set? That way you can see to that init-poller
thread causes timing issues for other tests.
* Change setup() in the TestCapacityScheduler to set init-poller to
ControlledJobInitializationPoller.
I do agree with the removing of job.kill() in killJob in FakeTaskTrackerManager
since mostly we are dealing only with status changes.
> testClusterBlockingForLackOfMemory in TestCapacityScheduler fails randomly
> --------------------------------------------------------------------------
>
> Key: HADOOP-5068
> URL: https://issues.apache.org/jira/browse/HADOOP-5068
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Sreekanth Ramakrishnan
> Assignee: Vinod K V
> Attachments: HADOOP-5068-20090120-git.txt
>
>
> testClusterBlockingForLackOfMemory fails randomly when TestCapacityScheduler
> is run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
