[ 
https://issues.apache.org/jira/browse/FLINK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327491#comment-15327491
 ] 

ASF GitHub Bot commented on FLINK-3937:
---------------------------------------

Github user rmetzger commented on the issue:

    https://github.com/apache/flink/pull/2085
  
    Detached per job submission is not working (`./bin/flink run -m 
yarn-cluster -yd -yn 1 ./examples/batch/WordCount.jar `)
    
    ```
    2016-06-13 07:28:22,423 INFO  org.apache.flink.yarn.ApplicationClient       
                - Trying to register at JobManager 
akka.tcp://flink@10.0.2.15:45521/user/jobmanager.
    2016-06-13 07:28:22,829 INFO  org.apache.flink.yarn.ApplicationClient       
                - Successfully registered at the ResourceManager using 
JobManager Actor[akka.tcp://flink@10.0.2.15:45521/user/jobmanager#1868998090]
    TaskManager status (0/1)
    TaskManager status (0/1)
    TaskManager status (0/1)
    TaskManager status (0/1)
    TaskManager status (0/1)
    TaskManager status (0/1)
    TaskManager status (0/1)
    TaskManager status (0/1)
    All TaskManagers are connected
    Cluster started
    Using address /10.0.2.15:45521 to connect to JobManager.
    JobManager web interface address 
http://quickstart.cloudera:8088/proxy/application_1447844011707_0039/
    Starting execution of program
    Executing WordCount example with default input data set.
    Use --input to specify file input.
    Printing result to stdout. Use --output to specify output path.
    
    ------------------------------------------------------------
     The program finished with the following exception:
    
    Job was submitted in detached mode. Results of job execution, such as 
accumulators, runtime, job id etc. are not available. Please make sure your 
program doesn't call an eager execution function [collect, print, printToErr, 
count]. 
        
org.apache.flink.client.program.DetachedEnvironment$DetachedJobExecutionResult.getAccumulatorResult(DetachedEnvironment.java:103)
        org.apache.flink.api.java.DataSet.collect(DataSet.java:412)
        org.apache.flink.api.java.DataSet.print(DataSet.java:1605)
        
org.apache.flink.examples.java.wordcount.WordCount.main(WordCount.java:92)
    2016-06-13 07:28:27,206 INFO  org.apache.flink.yarn.YarnClusterClient       
                - Disconnecting YarnClusterClient from ApplicationMaster
    2016-06-13 07:28:27,208 INFO  org.apache.flink.yarn.ApplicationClient       
                - Stopped Application client.
    2016-06-13 07:28:27,208 INFO  org.apache.flink.yarn.ApplicationClient       
                - Disconnect from JobManager 
Actor[akka.tcp://flink@10.0.2.15:45521/user/jobmanager#1868998090].
    2016-06-13 07:28:27,307 INFO  org.apache.flink.yarn.YarnClusterClient       
                - Application application_1447844011707_0039 finished with 
state RUNNING and final state UNDEFINED at 0
    [cloudera@quickstart build-target]
    ```
    
    In the JobManager logs, there is no sign of a job being submitted.


> 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)

Reply via email to