hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7920) Cleanup configuration of PlacementConstraints
Date Mon, 12 Feb 2018 03:32:00 GMT

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

Wangda Tan commented on YARN-7920:

Thanks [~kkaranasos], I would still prefer to "scheduler", otherwise it will be a duplicated
config to yarn.resourcemanager.scheduler, and once FS want to support the feature, we need
to add a new option and document, etc. We can add a check in the processor to throw an exception
if the configured scheduler is not CS, sounds like a plan?

> Cleanup configuration of PlacementConstraints
> ---------------------------------------------
>                 Key: YARN-7920
>                 URL: https://issues.apache.org/jira/browse/YARN-7920
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>            Priority: Blocker
> Currently it is very confusing to have the two configs in two different files (yarn-site.xml
and capacity-scheduler.xml). 
> Maybe a better approach is: we can delete the scheduling-request.allowed in CS, and update
placement-constraints configs in yarn-site.xml a bit: 
> - Remove placement-constraints.enabled, and add a new placement-constraints.handler,
by default is none, and other acceptable values are a. external-processor (since algorithm
is too generic to me), b. scheduler. 
> - And add a new PlacementProcessor just to pass SchedulingRequest to scheduler without
any modifications.

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