hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7370) Preemption properties should be refreshable
Date Thu, 02 Nov 2017 14:56:00 GMT

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

Eric Payne commented on YARN-7370:
----------------------------------

[~sunilg], thanks for your comment. I see what you mean. If we take out the {{if (this.csConfig
!= null)}}, then the values will also be logged during initialization as well as during refresh.
That way we can compare newly logged values with the initial ones.

[~GergelyNovak], Sorry for changing it at this point, but [~sunilg] has a good point. Would
you mind making this change?

> Preemption properties should be refreshable
> -------------------------------------------
>
>                 Key: YARN-7370
>                 URL: https://issues.apache.org/jira/browse/YARN-7370
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler, scheduler preemption
>    Affects Versions: 2.8.0, 3.0.0-alpha3
>            Reporter: Eric Payne
>            Assignee: Gergely Novák
>            Priority: Major
>         Attachments: YARN-7370.001.patch, YARN-7370.002.patch, YARN-7370.003.patch
>
>
> At least the properties for {{max-allowable-limit}} and {{minimum-threshold}} should
be refreshable. It would also be nice to make {{intra-queue-preemption.enabled}} and {{preemption-order-policy}}
refreshable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message