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

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

Github user mxm commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2085#discussion_r66806299
  
    --- Diff: docs/apis/cli.md ---
    @@ -252,6 +256,12 @@ Action "list" lists running and scheduled programs.
                                        configuration.
          -r,--running                  Show only running programs and their 
JobIDs
          -s,--scheduled                Show only scheduled programs and their 
JobIDs
    +  Additional arguments if -m yarn-cluster is set:
    +     -yid <yarnApplicationId>      YARN application ID of Flink YARN 
session to
    +                                   connect to. Must not be set if 
JobManager HA
    +                                   is used. In this case, JobManager RPC
    +                                   location is automatically retrieved from
    +                                   Zookeeper.
    --- End diff --
    
    Same as for `list` and `info`. I agree this verbosity is not very nice. 
Looking into how I can make this look nicer.


> 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