flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zhijiangW <...@git.apache.org>
Subject [GitHub] flink pull request #3457: [FLINK-5135][runtime] Expand the memory types in R...
Date Thu, 02 Mar 2017 10:50:01 GMT
GitHub user zhijiangW opened a pull request:


    [FLINK-5135][runtime] Expand the memory types in ResourceProfile related with ResourceSpec

    This is a part of fine-grained resource configuration in `flip6`
    The `JobManager` requests slot with `ResourceProfile` from `ResourceManager` before deployment.
Currently the `ResourceProfile` only contains cpu cores and memory fields. The memory should
be expanded to different types like heap memory, direct memory and native memory corresponding
with `ResourceSpec`.
    Further, the direct memory in `ResourceProfile` would be considered in `ContaineredTaskManagerParameters`
used to set JVM options before launching the `TaskManager` process.
    And some other related processes in runtime would be submitted later:
    1. `SlotPool` requests slot to get preferred resource from `JobVertex`, which is blocked
by [PR-3455](https://github.com/apache/flink/pull/3455)
    2. Sets the `ResourceProfile` to `TaskManager` by `ResourceManager`

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

    $ git pull https://github.com/zhijiangW/flink FLINK-5135

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


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3457
commit c1dcf48f2d5b3d444fba0f1cd23c7c0070621796
Author: 淘江 <taojiang.wzj@alibaba-inc.com>
Date:   2017-03-02T10:23:42Z

    [FLINK-5135][runtime]Expand the fields in ResourceProfile based on ResourceSpec


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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message