Github user zentol commented on a diff in the pull request:
https://github.com/apache/flink/pull/5506#discussion_r168752379
--- Diff: docs/_includes/generated/job_manager_configuration.html ---
@@ -9,67 +9,57 @@
<tbody>
<tr>
<td><h5>jobmanager.archive.fs.dir</h5></td>
- <td>(none)</td>
+ <td style="word-wrap: break-word;">(none)</td>
<td></td>
</tr>
<tr>
<td><h5>jobmanager.execution.attempts-history-size</h5></td>
- <td>16</td>
+ <td style="word-wrap: break-word;">16</td>
<td>The maximum number of prior execution attempts kept in
history.</td>
</tr>
<tr>
<td><h5>jobmanager.execution.failover-strategy</h5></td>
- <td>"full"</td>
+ <td style="word-wrap: break-word;">"full"</td>
<td>The maximum number of prior execution attempts kept in
history.</td>
</tr>
<tr>
<td><h5>jobmanager.heap.mb</h5></td>
- <td>1024</td>
+ <td style="word-wrap: break-word;">1024</td>
<td>JVM heap size (in megabytes) for the JobManager.</td>
</tr>
<tr>
<td><h5>jobmanager.resourcemanager.reconnect-interval</h5></td>
- <td>2000</td>
+ <td style="word-wrap: break-word;">2000</td>
<td>This option specifies the interval in order to trigger a
resource manager reconnection if the connection to the resource manager has
been lost. This option is only intended for internal use.</td>
</tr>
<tr>
<td><h5>jobmanager.rpc.address</h5></td>
- <td>(none)</td>
+ <td style="word-wrap: break-word;">(none)</td>
<td>The config parameter defining the network address to
connect to for communication with the job manager. This value is only
interpreted in setups where a single JobManager with static name or address
exists (simple standalone setups, or container setups with dynamic service name
resolution). It is not used in many high-availability setups, when a
leader-election service (like ZooKeeper) is used to elect and discover the
JobManager leader from potentially multiple standby JobManagers.</td>
</tr>
<tr>
<td><h5>jobmanager.rpc.port</h5></td>
- <td>6123</td>
+ <td style="word-wrap: break-word;">6123</td>
<td>The config parameter defining the network port to connect
to for communication with the job manager. Like jobmanager.rpc.address, this
value is only interpreted in setups where a single JobManager with static
name/address and port exists (simple standalone setups, or container setups
with dynamic service name resolution). This config option is not used in many
high-availability setups, when a leader-election service (like ZooKeeper) is
used to elect and discover the JobManager leader from potentially multiple
standby JobManagers.</td>
</tr>
<tr>
<td><h5>jobstore.cache-size</h5></td>
- <td>52428800</td>
+ <td style="word-wrap: break-word;">52428800</td>
<td>The job store cache size in bytes which is used to keep
completed jobs in memory.</td>
</tr>
<tr>
<td><h5>jobstore.expiration-time</h5></td>
- <td>3600</td>
+ <td style="word-wrap: break-word;">3600</td>
<td>The time in seconds after which a completed job expires
and is purged from the job store.</td>
</tr>
- <tr>
- <td><h5>slot.allocation.resourcemanager.timeout</h5></td>
--- End diff --
this option was recently removed
---
