[
https://issues.apache.org/jira/browse/YARN-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221064#comment-16221064
]
Eric Payne commented on YARN-6124:
----------------------------------
Thanks [~leftnoteasy]. I will document my findings and you can work on it when
you get to it. YARN-7370 doesn't depend on this JIRA, does it?
I got it to move past the NPE, but the changes I made may not be the best (it
may have other side effects):
{code}
public void serviceInit(Configuration conf) throws Exception {
Configuration configuration = new Configuration(conf);
- super.serviceInit(conf);
initScheduler(configuration);
+ super.serviceInit(conf);
}
{code}
Also, a quick test didn't seem to work. I started the RM with
{{yarn.resourcemanager.scheduler.monitor.enable}} set to {{true}}, changed it
to false, and then did {{-refreshQueues}}. It's going through the
{{updateSchedulingMonitors}} code but it doesn't change the value.
> Make SchedulingEditPolicy can be enabled / disabled / updated with RMAdmin
> -refreshQueues
> -----------------------------------------------------------------------------------------
>
> Key: YARN-6124
> URL: https://issues.apache.org/jira/browse/YARN-6124
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-6124.wip.1.patch, YARN-6124.wip.2.patch
>
>
> Now enabled / disable / update SchedulingEditPolicy config requires restart
> RM. This is inconvenient when admin wants to make changes to
> SchedulingEditPolicies.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
