lhotari commented on PR #25580: URL: https://github.com/apache/pulsar/pull/25580#issuecomment-4326125342
> Now that the BookKeeper client exposes these TCP keep-alive tuning knobs, the Pulsar Broker should also expose matching > configuration entries, so that operators can tune the TCP keep-alive behavior of the broker's > BookKeeper client without having to patch code or rely on OS-wide defaults. To solve the issues where connections stall, it's usually necessary to configure TCP keep-alive on both sides: the client and the server. Keep-alive is enabled by default for BookKeeper client and server, but they do rely on OS defaults. It will anyways be necessary to tune OS defaults since the BookKeeper server doesn't have a way to configure the keep-alive parameters. In cloud managed k8s nodes, the settings have reasonable values by default at least in GCP. ``` # sysctl -a |grep keepalive net.ipv4.tcp_keepalive_intvl = 60 net.ipv4.tcp_keepalive_probes = 5 net.ipv4.tcp_keepalive_time = 300 ``` -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
