[YARN-1007] [YARN-321] Enhance History Reader interface for Containers

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: YARN-321
• Fix Version/s: 2.4.0
• Assignee: Mayank Bansal
• Reporter: Devaraj Kavali
• Created: 01/Aug/13 14:46
• Updated: 10/Apr/14 13:12
• Resolved: 03/Aug/13 14:47

Description

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.

Issue Links

• blocks: YARN-975 Add a file-system implementation for history-storage