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

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

Github user rmetzger commented on the issue:

    https://github.com/apache/flink/pull/2085
  
    I quickly tried your changes.
    Some notes
    (1)  When listing the yarn-session.sh cli options, I could not see the 
newly added argument
    ```
    ./bin/yarn-session.sh 
    2016-06-10 09:28:37,186 ERROR org.apache.flink.yarn.cli.FlinkYarnSessionCli 
                - Missing required argument n
    Usage:
       Required
         -n,--container <arg>   Number of YARN container to allocate (=Number 
of Task Managers)
       Optional
         -D <arg>                        Dynamic properties
         -d,--detached                   Start detached
         -jm,--jobManagerMemory <arg>    Memory for JobManager Container [in MB]
         -nm,--name <arg>                Set a custom name for the application 
on YARN
         -q,--query                      Display available YARN resources 
(memory, cores)
         -qu,--queue <arg>               Specify YARN queue.
         -s,--slots <arg>                Number of slots per TaskManager
         -st,--streaming                 Start Flink in streaming mode
         -tm,--taskManagerMemory <arg>   Memory per TaskManager Container [in 
MB]
    Error while starting the YARN Client. Please check log output!
    ```
    
    (2) Starting a YARN session works. Also, connecting with a second YARN 
session works. However, if I'm stopping the session from the second session 
client, the first one does not notice this.
    It would be good if all connected clients receive the messages, instead of 
the last one connected.



> 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