flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1157) Document TaskManager Slots
Date Mon, 01 Dec 2014 18:02:12 GMT

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

ASF GitHub Bot commented on FLINK-1157:

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

    --- Diff: docs/config.md ---
    @@ -36,26 +39,29 @@ master/coordinator of the distributed system (DEFAULT: localhost).
     - `jobmanager.rpc.port`: The port number of the JobManager (DEFAULT: 6123).
     - `jobmanager.heap.mb`: JVM heap size (in megabytes) for the JobManager
    -(DEFAULT: 256).
    +(DEFAULT: 256). You may have to increase the heap size for the JobManager if you are
    +very large applications (with may operators), or if you are keeping a long history of
     - `taskmanager.heap.mb`: JVM heap size (in megabytes) for the TaskManagers,
     which are the parallel workers of the system. In
     contrast to Hadoop, Flink runs operators (e.g., join, aggregate) and
     user-defined functions (e.g., Map, Reduce, CoGroup) inside the TaskManager
     (including sorting/hashing/caching), so this value should be as
    -large as possible (DEFAULT: 512). On YARN setups, this value is automatically
    -configured to the size of the TaskManager's YARN container, minus a
    -certain tolerance value.
    +large as possible (DEFAULT: 512). If the cluster is exclusively running Flink,
    --- End diff --
    see comment for JM config

> Document TaskManager Slots
> --------------------------
>                 Key: FLINK-1157
>                 URL: https://issues.apache.org/jira/browse/FLINK-1157
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
> Slots are not explained in the documentation.

This message was sent by Atlassian JIRA

View raw message