hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7839) Check node capacity before placing in the Algorithm
Date Fri, 02 Feb 2018 17:05:01 GMT

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

Sunil G commented on YARN-7839:

bq.despite the naming, as far as I know, the candidateNodeSet is currently always only a single

[~kkaranasos] and [~asuresh] for multi node, CandidateNodeSet was ideal interface to extend
for. So multiple nodes could come in tat iterator.

> Check node capacity before placing in the Algorithm
> ---------------------------------------------------
>                 Key: YARN-7839
>                 URL: https://issues.apache.org/jira/browse/YARN-7839
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Panagiotis Garefalakis
>            Priority: Major
>         Attachments: YARN-7839-YARN-6592.001.patch
> Currently, the Algorithm assigns a node to a request purely based on if the constraints
are met. It is later in the scheduling phase that the Queue capacity and Node capacity are
checked. If the request cannot be placed because of unavailable Queue/Node capacity, the request
is retried by the Algorithm.
> For clusters that are running at high utilization, we can reduce the retries if we perform
the Node capacity check in the Algorithm as well. The Queue capacity check and the other user
limit checks can still be handled by the scheduler (since queues and other limits are tied
to the scheduler, and not scheduler agnostic)

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message