[ https://issues.apache.org/jira/browse/YARN-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216007#comment-16216007 ]
Wangda Tan commented on YARN-7370: ---------------------------------- Make sense, [~eepayne]. I just found previously I filed a JIRA: YARN-6124. Let's move enable/disable preemption to YARN-6124, and move preemption properties refresh to this JIRA. And FYI: I have a wip patch in YARN-6124, which should be directly ported to this JIRA to solve the problems (See {{syncConfigFromScheduler}} in attached patch of YARN-6124). > 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