| <table class="configuration 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: 10%">Type</th> |
| <th class="text-left" style="width: 55%">Description</th> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td><h5>heartbeat.interval</h5></td> |
| <td style="word-wrap: break-word;">10 s</td> |
| <td>Duration</td> |
| <td>Time interval between heartbeat RPC requests from the sender to the receiver side.</td> |
| </tr> |
| <tr> |
| <td><h5>heartbeat.rpc-failure-threshold</h5></td> |
| <td style="word-wrap: break-word;">2</td> |
| <td>Integer</td> |
| <td>The number of consecutive failed heartbeat RPCs until a heartbeat target is marked as unreachable. Failed heartbeat RPCs can be used to detect dead targets faster because they no longer receive the RPCs. The detection time is <code class="highlighter-rouge">heartbeat.interval</code> * <code class="highlighter-rouge">heartbeat.rpc-failure-threshold</code>. In environments with a flaky network, setting this value too low can produce false positives. In this case, we recommend to increase this value, but not higher than <code class="highlighter-rouge">heartbeat.timeout</code> / <code class="highlighter-rouge">heartbeat.interval</code>. The mechanism can be disabled by setting this option to <code class="highlighter-rouge">-1</code></td> |
| </tr> |
| <tr> |
| <td><h5>heartbeat.timeout</h5></td> |
| <td style="word-wrap: break-word;">50 s</td> |
| <td>Duration</td> |
| <td>Timeout for requesting and receiving heartbeats for both sender and receiver sides.</td> |
| </tr> |
| </tbody> |
| </table> |
