hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-1007) [YARN-321] Enhance History Reader interface for Containers
Date Thu, 01 Aug 2013 14:47:48 GMT
Devaraj K created YARN-1007:

             Summary: [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: Devaraj K

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. 

  Collection<ContainerHistoryData> getContainers(
      ApplicationAttemptId appAttemptId);

  Collection<ContainerHistoryData> getContainers(ApplicationId appId);

   * This method returns {@link Container} for specified {@link ContainerId}.
   * @param {@link ContainerId}
   * @return {@link Container} for ContainerId
  ContainerHistoryData getAMContainer(ContainerId containerId);
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.

   * This method returns {@link ContainerHistoryData} for specified
   * {@link ApplicationAttemptId}.
   * @param {@link ApplicationAttemptId}
   * @return {@link ContainerHistoryData} for ApplicationAttemptId
  ContainerHistoryData getContainer(ApplicationAttemptId appAttemptId);
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

View raw message