HuangZhenQiu commented on a change in pull request #11541:
[FLINK-15416][network] add task manager netty client retry mechenism
URL: https://github.com/apache/flink/pull/11541#discussion_r404518845
##########
File path:
docs/_includes/generated/netty_shuffle_environment_configuration.html
##########
@@ -57,17 +57,23 @@
<td>Number of extra network buffers to use for each
outgoing/incoming gate (result partition/input gate). In credit-based flow
control mode, this indicates how many floating credits are shared among all the
input channels. The floating buffers are distributed based on backlog
(real-time output buffers in the subpartition) feedback, and can help relieve
back-pressure caused by unbalanced data distribution among the subpartitions.
This value should be increased in case of higher round trip times between nodes
and/or larger number of machines in the cluster.</td>
</tr>
<tr>
-
<td><h5>taskmanager.network.netty.client.connectTimeoutSec</h5></td>
- <td style="word-wrap: break-word;">120</td>
+ <td><h5>taskmanager.network.retries</h5></td>
+ <td style="word-wrap: break-word;">0</td>
<td>Integer</td>
- <td>The Netty client connection timeout.</td>
+ <td>The number of retry attempts for network communication.
Currently it's only used for establishing input/output channel connections</td>
</tr>
<tr>
<td><h5>taskmanager.network.netty.client.numThreads</h5></td>
<td style="word-wrap: break-word;">-1</td>
<td>Integer</td>
<td>The number of Netty client threads.</td>
</tr>
+ <tr>
+ <td><h5>taskmanager.network.netty.clientRetry</h5></td>
Review comment:
It is a mistake. I manually changed the file. I will change it back.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
