[
https://issues.apache.org/jira/browse/MYRIAD-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074183#comment-15074183
]
DarinJ commented on MYRIAD-184:
-------------------------------
Just checked this for appropriate behavior. If one sets
yarn.resourcemanager.webapp.address to <rm.hostname.com>:8090, the config is
downloaded as expected (assuming remote dist as that's the only time the config
is downloaded). You will have issues if you set it to 0.0.0.0:8090 though.
I suppose we could check for the 0.0.0.0 and replace with
yarn.resourcemanager.hostname.
> RM Ports are Hardcoded in NMExecutorCLGenImpl.java
> --------------------------------------------------
>
> Key: MYRIAD-184
> URL: https://issues.apache.org/jira/browse/MYRIAD-184
> Project: Myriad
> Issue Type: Bug
> Components: Executor
> Affects Versions: Myriad 0.1.0
> Reporter: John Omernik
>
> In NMExecutorCLGenImpl.java, the ports for Resource Manager are derived via
> the http.policy config setting. Instead, the ports should be using a
> different variable that actually corresponds to running port. The ports that
> are hard coded are the default ports for the RM for HTTP and HTTPS (8088, and
> 8090) but if a user changed the port, the config download would fail. Thus
> finding a better variable here would help make it so operators are not
> limited to the default ports in their environments.
> (Hard Coding in function public String getConfigurationUrl())
> https://github.com/apache/incubator-myriad/blob/df7d05c8639b371b94a1e94406e2f2446d10eaaf/myriad-scheduler/src/main/java/org/apache/myriad/scheduler/NMExecutorCLGenImpl.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
