You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yangze Guo (Jira)" <ji...@apache.org> on 2023/06/28 11:56:00 UTC
[jira] [Closed] (FLINK-32191) Support for configuring tcp keepalive related parameters.
[ https://issues.apache.org/jira/browse/FLINK-32191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yangze Guo closed FLINK-32191.
------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
> Support for configuring tcp keepalive related parameters.
> ---------------------------------------------------------
>
> Key: FLINK-32191
> URL: https://issues.apache.org/jira/browse/FLINK-32191
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Reporter: dizhou cao
> Assignee: Weihua Hu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> We encountered a case in our production environment where the netty client was unable to send data to the server due to an abnormality in the switch link. However, client can only detect the abnormality after RTO timeout retransmission failure, which takes about 15 minutes in our production environment. This may result in a 15-minute job unavailability. We hope to perform failover and reschedule job more quickly. Flink has already enabled keepalive, but the default keepalive idle time is 2 hours. We can adjust the timeout of TCP keepalive by configuring TCP_KEEPIDLE, TCP_KEEPINTERVAL, and TCP_KEEPCOUNT. These configurations are already supported at the Netty.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)