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

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

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

    https://github.com/apache/flink/pull/5471#discussion_r167852941
  
    --- Diff: docs/ops/config.md ---
    @@ -268,59 +268,7 @@ These parameters configure the default HDFS used by 
Flink. Setups that do not sp
     
     ### TaskManager
     
    -The following parameters configure Flink's TaskManagers.
    -
    -
    -- `taskmanager.hostname`: The hostname of the network interface that the 
TaskManager binds to. By default, the TaskManager searches for network 
interfaces that can connect to the JobManager and other TaskManagers. This 
option can be used to define a hostname if that strategy fails for some reason. 
Because different TaskManagers need different values for this option, it 
usually is specified in an additional non-shared TaskManager-specific config 
file.
    -
    -- `taskmanager.rpc.port`: The task manager's IPC port (DEFAULT: **0**, 
which lets the OS choose a free port). Flink also accepts a list of ports 
("50100,50101"), ranges ("50100-50200") or a combination of both. It is 
recommended to set a range of ports to avoid collisions when multiple 
TaskManagers are running on the same machine.
    -
    -- `taskmanager.data.port`: The task manager's port used for data exchange 
operations (DEFAULT: **0**, which lets the OS choose a free port).
    -
    -- `taskmanager.data.ssl.enabled`: Enable SSL support for the taskmanager 
data transport. This is applicable only when the global ssl flag 
security.ssl.enabled is set to true (DEFAULT: **true**)
    -
    -- `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.
    -
    -- `taskmanager.numberOfTaskSlots`: The number of parallel operator or user 
function instances that a single TaskManager can run (DEFAULT: **1**). If this 
value is larger than 1, a single TaskManager takes multiple instances of a 
function or operator. That way, the TaskManager can utilize multiple CPU cores, 
but at the same time, the available memory is divided between the different 
operator or function instances. This value is typically proportional to the 
number of physical CPU cores that the TaskManager's machine has (e.g., equal to 
the number of cores, or half the number of cores).
    -
    -- `taskmanager.tmp.dirs`: The directory for temporary files, or a list of 
directories separated by the system's directory delimiter (for example ':' 
(colon) on Linux/Unix). If multiple directories are specified, then the 
temporary files will be distributed across the directories in a round robin 
fashion. The I/O manager component will spawn one reading and one writing 
thread per directory. A directory may be listed multiple times to have the I/O 
manager use multiple threads for it (for example if it is physically stored on 
a very fast disc or RAID) (DEFAULT: **The system's tmp dir**).
    -
    -- `taskmanager.network.memory.fraction`: Fraction of JVM memory to use for 
network buffers. This determines how many streaming data exchange channels a 
TaskManager can have at the same time and how well buffered the channels are. 
If a job is rejected or you get a warning that the system has not enough 
buffers available, increase this value or the min/max values below. Also note, 
that `taskmanager.network.memory.min` and `taskmanager.network.memory.max` may 
override this fraction. (DEFAULT: **0.1**)
    --- End diff --
    
    Why not include the longer description?


> Move remaining sections to generated tables
> -------------------------------------------
>
>                 Key: FLINK-8475
>                 URL: https://issues.apache.org/jira/browse/FLINK-8475
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Configuration
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>             Fix For: 1.5.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to