[
https://issues.apache.org/jira/browse/FLINK-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105298#comment-15105298
]
ASF GitHub Bot commented on FLINK-2935:
---------------------------------------
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1500#issuecomment-172531939
I have to correct myself. This should not be an issue if you start a Yarn
cluster in HA and then use `bin/flink run ...`, because a
`LeaderRetrievalService` will be instantiated which will take care of this.
However, it should be a problem here. The `FlinkILoop` instantiates a
`ScalaShellRemoteEnvironment` which is a sub class of `RemoteEnvironment`.
Since `RemoteEnvironment` is called with `null` for the client configuration,
it cannot find a possible ZooKeeper instance where the `JobManager` is
registered in the HA case. I think you have to forward the `Configuration`
object created from `flink-conf.yaml` to the `RemoteEnvironment` in order to
make it work.
> Allow scala shell to read yarn properties
> -----------------------------------------
>
> Key: FLINK-2935
> URL: https://issues.apache.org/jira/browse/FLINK-2935
> Project: Flink
> Issue Type: Improvement
> Components: Scala Shell
> Affects Versions: 0.9.1
> Reporter: Johannes
> Assignee: Chiwan Park
> Priority: Minor
> Labels: easyfix
>
> Currently the deployment of flink via yarn and the scala shell are not linked.
> When deploying a yarn session the file
> bq. org.apache.flink.client.CliFrontend
> creates a
> bq. .yarn-properties-$username
> file with the connection properties.
> There should be a way to have the scala shell automatically read this file if
> wanted as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
