[
https://issues.apache.org/jira/browse/YARN-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511705#comment-16511705
]
Young Chen commented on YARN-7708:
----------------------------------
Thanks [~botong] for the comments. I've fixed all of your suggestions except
for moving the properties to the YarnConfiguration. Since this
LoadBasedGlobalPolicy is pluggable, and may not be in use at times, is it still
considered good practice to put the properties inside YarnConfiguration? I feel
that this might lead to excessive bloat in the already very large configuration
file.
In addition, I also changed scaling to be an enum. I think this should be
cleaner than arbitrary strings.
[^YARN-7708-YARN-7402.03.patch]
> [GPG] Load based policy generator
> ---------------------------------
>
> Key: YARN-7708
> URL: https://issues.apache.org/jira/browse/YARN-7708
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Carlo Curino
> Assignee: Young Chen
> Priority: Major
> Attachments: YARN-7708-YARN-7402.01.cumulative.patch,
> YARN-7708-YARN-7402.01.patch, YARN-7708-YARN-7402.02.cumulative.patch,
> YARN-7708-YARN-7402.02.patch, YARN-7708-YARN-7402.03.cumulative.patch,
> YARN-7708-YARN-7402.03.patch, YARN-7708-YARN-7402.04.cumulative.patch,
> YARN-7708-YARN-7402.05.cumulative.patch,
> YARN-7708-YARN-7402.06.cumulative.patch,
> YARN-7708-YARN-7402.07.cumulative.patch
>
>
> This policy reads load from the "pendingQueueLength" metrics and provides
> scaling into a set of weights that influence the AMRMProxy and Router
> behaviors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
