[
https://issues.apache.org/jira/browse/YARN-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213017#comment-16213017
]
Wangda Tan commented on YARN-7370:
----------------------------------
[~GergelyNovak], you're very much welcome to take up this task, this is quite
helpful and important for user to use preemption.
I agree with Eric, it's better to include this in {{-refreshQueues}} op so we
don't need any changes to RMAdmin protocol and CLI. To me the requirement is:
- Handle changes to {{SchedulingEditPolicy}} configs including preemption
(which means {{SchedulingMonitor}} should be refreshable as well).
- All preemption-related parameters.
[~eepayne]/[~sunilg], please feel free to add any requirement in your mind.
> Intra-queue 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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
