| <table class="table table-bordered"> |
| <thead> |
| <tr> |
| <th class="text-left" style="width: 20%">Key</th> |
| <th class="text-left" style="width: 15%">Default</th> |
| <th class="text-left" style="width: 65%">Description</th> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td><h5>akka.ask.timeout</h5></td> |
| <td style="word-wrap: break-word;">"10 s"</td> |
| <td>Timeout used for all futures and blocking Akka calls. If Flink fails due to timeouts then you should try to increase this value. Timeouts can be caused by slow machines or a congested network. The timeout value requires a time-unit specifier (ms/s/min/h/d).</td> |
| </tr> |
| <tr> |
| <td><h5>akka.client.timeout</h5></td> |
| <td style="word-wrap: break-word;">"60 s"</td> |
| <td>Timeout for all blocking calls on the client side.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.framesize</h5></td> |
| <td style="word-wrap: break-word;">"10485760b"</td> |
| <td>Maximum size of messages which are sent between the JobManager and the TaskManagers. If Flink fails because messages exceed this limit, then you should increase it. The message size requires a size-unit specifier.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.jvm-exit-on-fatal-error</h5></td> |
| <td style="word-wrap: break-word;">true</td> |
| <td>Exit JVM on fatal Akka errors.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.log.lifecycle.events</h5></td> |
| <td style="word-wrap: break-word;">false</td> |
| <td>Turns on the Akka’s remote logging of events. Set this value to ‘true’ in case of debugging.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.lookup.timeout</h5></td> |
| <td style="word-wrap: break-word;">"10 s"</td> |
| <td>Timeout used for the lookup of the JobManager. The timeout value has to contain a time-unit specifier (ms/s/min/h/d).</td> |
| </tr> |
| <tr> |
| <td><h5>akka.retry-gate-closed-for</h5></td> |
| <td style="word-wrap: break-word;">50</td> |
| <td>Milliseconds a gate should be closed for after a remote connection was disconnected.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.ssl.enabled</h5></td> |
| <td style="word-wrap: break-word;">true</td> |
| <td>Turns on SSL for Akka’s remote communication. This is applicable only when the global ssl flag security.ssl.enabled is set to true.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.startup-timeout</h5></td> |
| <td style="word-wrap: break-word;">(none)</td> |
| <td>Timeout after which the startup of a remote component is considered being failed.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.tcp.timeout</h5></td> |
| <td style="word-wrap: break-word;">"20 s"</td> |
| <td>Timeout for all outbound connections. If you should experience problems with connecting to a TaskManager due to a slow network, you should increase this value.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.throughput</h5></td> |
| <td style="word-wrap: break-word;">15</td> |
| <td>Number of messages that are processed in a batch before returning the thread to the pool. Low values denote a fair scheduling whereas high values can increase the performance at the cost of unfairness.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.transport.heartbeat.interval</h5></td> |
| <td style="word-wrap: break-word;">"1000 s"</td> |
| <td>Heartbeat interval for Akka’s transport failure detector. Since Flink uses TCP, the detector is not necessary. Therefore, the detector is disabled by setting the interval to a very high value. In case you should need the transport failure detector, set the interval to some reasonable value. The interval value requires a time-unit specifier (ms/s/min/h/d).</td> |
| </tr> |
| <tr> |
| <td><h5>akka.transport.heartbeat.pause</h5></td> |
| <td style="word-wrap: break-word;">"6000 s"</td> |
| <td>Acceptable heartbeat pause for Akka’s transport failure detector. Since Flink uses TCP, the detector is not necessary. Therefore, the detector is disabled by setting the pause to a very high value. In case you should need the transport failure detector, set the pause to some reasonable value. The pause value requires a time-unit specifier (ms/s/min/h/d).</td> |
| </tr> |
| <tr> |
| <td><h5>akka.transport.threshold</h5></td> |
| <td style="word-wrap: break-word;">300.0</td> |
| <td>Threshold for the transport failure detector. Since Flink uses TCP, the detector is not necessary and, thus, the threshold is set to a high value.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.watch.heartbeat.interval</h5></td> |
| <td style="word-wrap: break-word;">"10 s"</td> |
| <td>Heartbeat interval for Akka’s DeathWatch mechanism to detect dead TaskManagers. If TaskManagers are wrongly marked dead because of lost or delayed heartbeat messages, then you should decrease this value or increase akka.watch.heartbeat.pause. A thorough description of Akka’s DeathWatch can be found <a href="http://doc.akka.io/docs/akka/snapshot/scala/remoting.html#failure-detector">here</a>.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.watch.heartbeat.pause</h5></td> |
| <td style="word-wrap: break-word;">"60 s"</td> |
| <td>Acceptable heartbeat pause for Akka’s DeathWatch mechanism. A low value does not allow an irregular heartbeat. If TaskManagers are wrongly marked dead because of lost or delayed heartbeat messages, then you should increase this value or decrease akka.watch.heartbeat.interval. Higher value increases the time to detect a dead TaskManager. A thorough description of Akka’s DeathWatch can be found <a href="http://doc.akka.io/docs/akka/snapshot/scala/remoting.html#failure-detector">here</a>.</td> |
| </tr> |
| <tr> |
| <td><h5>akka.watch.threshold</h5></td> |
| <td style="word-wrap: break-word;">12</td> |
| <td>Threshold for the DeathWatch failure detector. A low value is prone to false positives whereas a high value increases the time to detect a dead TaskManager. A thorough description of Akka’s DeathWatch can be found <a href="http://doc.akka.io/docs/akka/snapshot/scala/remoting.html#failure-detector">here</a>.</td> |
| </tr> |
| </tbody> |
| </table> |
