hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1007) [YARN-321] Enhance History Reader interface for Containers
Date Fri, 02 Aug 2013 21:09:52 GMT

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

Hadoop QA commented on YARN-1007:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12595668/YARN-1007-1.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1648//console

This message is automatically generated.
                
> [YARN-321] Enhance History Reader interface for Containers
> ----------------------------------------------------------
>
>                 Key: YARN-1007
>                 URL: https://issues.apache.org/jira/browse/YARN-1007
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: YARN-321
>            Reporter: Devaraj K
>            Assignee: Mayank Bansal
>         Attachments: YARN-1007-1.patch
>
>
> If we want to show the containers used by application/app attempt, We need to have two
more API's which returns collection of ContainerHistoryData for application id and applcation
attempt id something like below. 
> {code:xml}
>   Collection<ContainerHistoryData> getContainers(
>       ApplicationAttemptId appAttemptId);
>   Collection<ContainerHistoryData> getContainers(ApplicationId appId);
> {code}
> {code:xml}
>   /**
>    * This method returns {@link Container} for specified {@link ContainerId}.
>    * 
>    * @param {@link ContainerId}
>    * @return {@link Container} for ContainerId
>    */
>   ContainerHistoryData getAMContainer(ContainerId containerId);
> {code}
> In the above API, we need to change the argument to application attempt id or we can
remove this API because every attempt history data has master container id field, using master
container id, history data can get using this below API if it takes argument as container
id.
> {code:xml}
>   /**
>    * This method returns {@link ContainerHistoryData} for specified
>    * {@link ApplicationAttemptId}.
>    * 
>    * @param {@link ApplicationAttemptId}
>    * @return {@link ContainerHistoryData} for ApplicationAttemptId
>    */
>   ContainerHistoryData getContainer(ApplicationAttemptId appAttemptId);
> {code}
> Here application attempt can use numbers of containers but we cannot choose which container
history data to return. This API argument also need to be changed to take container id instead
of app attempt id. 

--
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

Mime
View raw message