[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Joseph Evans updated MAPREDUCE-3050:
-------------------------------------------

    Attachment: MR-3050.txt

This is the first draft of the patch.  It is intended mostly for feedback on 
the APIs that I am adding to YarnScheduler.

{code}
  /**
   * Get the Scheduler app for a given app attempt Id.
   * @param appAttemptId the id of the application attempt
   * @return SchedulerApp for this given attempt.
   */
  @Private
  @Stable
  SchedulerApp getApplication(ApplicationAttemptId appAttemptId);

  /**
   * Get the root queue for the scheduler.
   * @return the root queue for the scheduler.
   */
  @Private
  @Evolving
  Queue getRootQueue();
{code}

ShedulerApp is changed to SchedulerAppImpl and a new interface ScheduelerApp is 
created.

{code}
@Evolving
@LimitedPrivate("yarn")
public interface SchedulerApp {
  public Collection<RMContainer> getLiveContainers();
  public Collection<RMContainer> getReservedContainers();
  public boolean isPending();
}
{code}

Any feedback on this is appreciated.

> YarnScheduler needs to expose Resource Usage Information
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-3050
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3050
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>             Fix For: 0.23.0, 0.24.0
>
>         Attachments: MR-3050.txt
>
>
> Before the recent refactor The nodes had information in them about how much 
> resources they were using.  This information is not hidden inside 
> SchedulerNode.  Similarly resource usage information about an application, or 
> in aggregate is only available through the Scheduler and there is not 
> interface to pull it out.
> We need to expose APIs to get Resource and Container information from the 
> scheduler, in aggregate across the entire cluster, per application, per node, 
> and ideally also per queue if applicable (although there are no JIRAs I am 
> aware of that need this right now).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to