You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2013/09/14 05:55:52 UTC

[jira] [Commented] (YARN-879) Fix tests w.r.t o.a.h.y.server.resourcemanager.Application

    [ https://issues.apache.org/jira/browse/YARN-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767356#comment-13767356 ] 

Junping Du commented on YARN-879:
---------------------------------

Thanks [~devaraj.k] for review and comments!
1.2. Sure. Will update it soon.
3. Looks like resourcemanager here is not actually started, so no dispatcher service (and handler for SchedulerEvent) is running.
Can we bypass dispatcher here and go to scheduler to handle SchedulerEvent directly given we are testing scheduler logic and other tests already cover tests of different dispatchers? 
                
> Fix tests w.r.t o.a.h.y.server.resourcemanager.Application
> ----------------------------------------------------------
>
>                 Key: YARN-879
>                 URL: https://issues.apache.org/jira/browse/YARN-879
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: YARN-879.patch, YARN-879-v2.patch, YARN-879-v3.patch
>
>
> getResources() will return a list of containers that allocated by RM. However, it is now return null directly. The worse thing is: if LOG.debug is enabled, then it will definitely cause NPE exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira