[
https://issues.apache.org/jira/browse/YARN-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226600#comment-15226600
]
Sunil G commented on YARN-4514:
-------------------------------
bq.we expect this configuration to be configured by user during deployment.
Right ?
I say admin. But more or less its a user.
bq.namespaces like ws/v1/cluster, etc. move to constants.js
I still say these are config than constants. .Because some of the rest
namespace end points can be added in future, and may get changed too. So it ll
help in upgrades etc. I looked TEZ code, and they use this as config too.
Thoughts?
bq.maybe we can have a separate config for scheme(http/https)
Yes, I will address the same.
bq.I think we wont require localBaseUrl(which is corsproxy URL) in normal
production cluster
We can use localBaseUrl and keep it as empty for now. And for tests, we can
configure {{corsproxy}} URL in testbed.
I will also change the config name from default to address as discussed offline.
> [YARN-3368] Cleanup hardcoded configurations, such as RM/ATS addresses
> ----------------------------------------------------------------------
>
> Key: YARN-4514
> URL: https://issues.apache.org/jira/browse/YARN-4514
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Sunil G
> Attachments: YARN-4514-YARN-3368.1.patch, YARN-4514-YARN-3368.2.patch
>
>
> We have several configurations are hard-coded, for example, RM/ATS addresses,
> we should make them configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
