GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/4271

    [FLINK-7113] Make ClusterDescriptor independent of cluster size

    This PR is based on #4270.
    
    In order to pull some of the cluster deployment logic out of the 
`AbstractYarnClusterDescriptor`, this PR introduces a `ClusterSpecification`. 
This specification contains information about the size of the cluster to be 
started. Instead of setting these values via setters directly on the 
`ClusterDescriptor`, we provide the information at deployment time via the 
`ClusterSpecification`.
    
    The way I envision the `ClusterDescriptor` to work, is to only contain 
information which is necessary to talk to a resource manager, such as Mesos or 
Yarn. All Flink cluster specific information should be provided to the `deploy` 
methods. This also allows us better share code between different 
`ClusterDescriptor`, e.g. Mesos and Yarn.
    
    This is only the start of a refactoring of the `ClusterDescriptor`. Much 
more information can be pulled out of the `AbstractYarnClusterDescriptor`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink refactorClusterDescriptor

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/4271.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 #4271
    
----
commit 9cfb9718d7b64e253aaf636dc17b8939e2592a98
Author: Till Rohrmann <trohrm...@apache.org>
Date:   2017-07-06T07:33:18Z

    [FLINK-7110] [client] Add per-job cluster deployment interface

commit 0143d7e33b7d99ce8371e455458b730ba2c13d06
Author: Till Rohrmann <trohrm...@apache.org>
Date:   2017-07-06T12:00:21Z

    [FLINK-7113] Make ClusterDescriptor independent of cluster size
    
    The deploySession method now is given a ClusterSpecification which 
specifies the
    size of the cluster which it is supposed to deploy.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to