I looked at the commit you cherry-picked and nothing in there explains the error you got. This rather sounds like something might be mixed up between (remaining artefacts of) flink 1.3 and 1.2.
Can you verify that nothing of your flink 1.3 tests remains, e.g. running JobManager or TaskManager instances? Also that you're not accidentally running the yarn-session.sh script of 1.3? Nico On Wednesday, 6 September 2017 06:36:42 CEST Sunny Yun wrote: > Hi, > > Using flink 1.2.0, I faced to issue > https://issues.apache.org/jira/browse/FLINK-6117 > https://issues.apache.org/jira/browse/FLINK-6117. > This issue is fixed at version 1.3.0. But I have some reason to trying to > find out work around. > > I did, > 1. change source according to > https://github.com/apache/flink/commit/eef85e095a8a0e4c4553631b74ba7b9f173ce > bf0 2. replace $FLINK_HOME/lib/flink-dist_2.11-1.2.0.jar > 3. set flink-conf.yaml "zookeeper.sasl.disable: true" > 4. run yarn-session.sh > > > Original problem-Authentication failed- seems to be passed. > But I got this error, > > Exception in thread "main" java.lang.RuntimeException: Failed to retrieve > JobManager address > at > org.apache.flink.client.program.ClusterClient.getJobManagerAddress(ClusterCl > ient.java:248) at > org.apache.flink.yarn.cli.FlinkYarnSessionCli.run(FlinkYarnSessionCli.java:6 > 27) at > org.apache.flink.yarn.cli.FlinkYarnSessionCli$1.call(FlinkYarnSessionCli.jav > a:476) at > org.apache.flink.yarn.cli.FlinkYarnSessionCli$1.call(FlinkYarnSessionCli.jav > a:473) at > org.apache.flink.runtime.security.HadoopSecurityContext$1.run(HadoopSecurity > Context.java:43) at java.security.AccessController.doPrivileged(Native > Method) at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.ja > va:1656) at > org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSec > urityContext.java:40) at > org.apache.flink.yarn.cli.FlinkYarnSessionCli.main(FlinkYarnSessionCli.java: > 473) Caused by: > org.apache.flink.runtime.leaderretrieval.LeaderRetrievalException: Could > not retrieve the leader address and leader session ID. > at > org.apache.flink.runtime.util.LeaderRetrievalUtils.retrieveLeaderConnectionI > nfo(LeaderRetrievalUtils.java:175) at > org.apache.flink.client.program.ClusterClient.getJobManagerAddress(ClusterCl > ient.java:242) ... 9 more > Caused by: java.util.concurrent.TimeoutException: Futures timed out after > [60000 milliseconds] > at > scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219) > at > scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223) > at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:190) > at > scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scal > a:53) at scala.concurrent.Await$.result(package.scala:190) > at scala.concurrent.Await.result(package.scala) > at > org.apache.flink.runtime.util.LeaderRetrievalUtils.retrieveLeaderConnectionI > nfo(LeaderRetrievalUtils.java:173) ... 10 more > > > I believe related setting(flink, hadoop, zookeeper) is correct. Because > yarn-session works smoothly with flink 1.3.2 in same environment. > > Does anyone have any inspiration for this error message? > > Thanks. > > ᐧ
signature.asc
Description: This is a digitally signed message part.
