[
https://issues.apache.org/jira/browse/FLINK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321130#comment-15321130
]
ASF GitHub Bot commented on FLINK-3937:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2085
[FLINK-3937] programmatic resuming of clusters
These changes are based on #1978 and #2034. More specifically, they port
resuming of running Yarn clusters from #2034 to the refactoring of #1978. The
abstraction in place enables us to plug in other cluster frameworks in the
future.
- integrates with and extends the refactoring of FLINK-3667
- enables to resume from Yarn properties or Yarn application id
- introduces additional StandaloneClusterDescriptor
- introduces DefaultCLI to get rid of standalone mode switches in
CliFrontend
- various fixes and improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-3937
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2085.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2085
----
commit b144e64758a95bcac33bd0ac91ab7eefaf4040e9
Author: Maximilian Michels <m...@apache.org>
Date: 2016-04-22T17:52:54Z
[FLINK-3667] refactor client communication classes
- ClusterDescriptor: base interface for cluster deployment descriptors
- ClusterDescriptor: YarnClusterDescriptor
- ClusterClient: base class for ClusterClients, handles lifecycle of cluster
- ClusterClient: shares configuration with the implementations
- ClusterClient: StandaloneClusterClient, YarnClusterClient
- ClusterClient: remove run methods and enable detached mode via flag
- CliFrontend: remove all Yarn specific logic
- CliFrontend: remove all cluster setup logic
- CustomCommandLine: interface for other cluster implementations
- Customcommandline: enables creation of new cluster or resuming from
existing
- Yarn: move Yarn classes and functionality to the yarn module (yarn
properties, yarn interfaces)
- Yarn: improve reliability of cluster startup
- Yarn Tests: only disable parallel execution of ITCases
commit 73524c89854f04ac41f0c288d9ebf8ef5efe628b
Author: Sebastian Klemke <sebastian.kle...@researchgate.net>
Date: 2016-05-25T12:28:59Z
[FLINK-3937] implement -yid option to Flink CLI
- enables to use list, savepoint, cancel and stop subcommands
- adapt FlinkYarnSessionCli to also accept YARN application Id to attach to
- update documentation
commit 1db8c97c39c2bf071db018c1ca505409c847a30b
Author: Maximilian Michels <m...@apache.org>
Date: 2016-06-01T10:45:52Z
[FLINK-3863] Yarn Cluster shutdown may fail if leader changed recently
commit 1a154fb12474a8630cce7e764d72398513055887
Author: Maximilian Michels <m...@apache.org>
Date: 2016-06-02T14:28:51Z
[FLINK-3937] programmatic resuming of clusters
- integrates with and extends the refactoring of FLINK-3667
- enables to resume from Yarn properties or Yarn application id
- introduces additional StandaloneClusterDescriptor
- introduces DefaultCLI to get rid of standalone mode switches in
CliFrontend
- various fixes and improvements
----
> 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)
