[ https://issues.apache.org/jira/browse/FLINK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327413#comment-15327413 ]
ASF GitHub Bot commented on FLINK-3937: --------------------------------------- Github user rmetzger commented on a diff in the pull request: https://github.com/apache/flink/pull/2085#discussion_r66794640 --- Diff: docs/apis/cli.md --- @@ -105,6 +105,10 @@ The command line can be used to ./bin/flink list -r +- List running Flink jobs inside Flink YARN session: + + ./bin/flink list -m yarn-cluster -yid <yarnApplicationID> -r --- End diff -- This is a similar thing: ``` [cloudera@quickstart build-target]$ ./bin/flink list -m yarn-cluster -yid obiouslyWrong -r ------------------------------------------------------------ The program finished with the following exception: org.apache.flink.runtime.leaderretrieval.LeaderRetrievalException: Could not retrieve the leader gateway at org.apache.flink.runtime.util.LeaderRetrievalUtils.retrieveLeaderGateway(LeaderRetrievalUtils.java:127) at org.apache.flink.client.CliFrontend.getJobManagerGateway(CliFrontend.java:844) at org.apache.flink.client.CliFrontend.list(CliFrontend.java:378) at org.apache.flink.client.CliFrontend.parseParameters(CliFrontend.java:986) at org.apache.flink.client.CliFrontend.main(CliFrontend.java:1034) Caused by: java.util.concurrent.TimeoutException: Futures timed out after [10000 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:107) at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53) at scala.concurrent.Await$.result(package.scala:107) at scala.concurrent.Await.result(package.scala) at org.apache.flink.runtime.util.LeaderRetrievalUtils.retrieveLeaderGateway(LeaderRetrievalUtils.java:125) ... 4 more [cloudera@quickstart build-target]$ ``` > Make flink cli list, savepoint, cancel and stop work on Flink-on-YARN clusters > ------------------------------------------------------------------------------ > > Key: FLINK-3937 > URL: https://issues.apache.org/jira/browse/FLINK-3937 > Project: Flink > Issue Type: Improvement > Reporter: Sebastian Klemke > Assignee: Maximilian Michels > Priority: Trivial > Attachments: improve_flink_cli_yarn_integration.patch > > > Currently, flink cli can't figure out JobManager RPC location for > Flink-on-YARN clusters. Therefore, list, savepoint, cancel and stop > subcommands are hard to invoke if you only know the YARN application ID. As > an improvement, I suggest adding a -yid <yarnApplicationId> option to the > mentioned subcommands that can be used together with -m yarn-cluster. Flink > cli would then retrieve JobManager RPC location from YARN ResourceManager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)