lhotari commented on PR #25580: URL: https://github.com/apache/pulsar/pull/25580#issuecomment-4326581892
> > Sidenote: there's been a proposal to add keepalive to Pulsar components, but that was rejected in #14841. For broker connections, we rely on Pulsar's application level keep-alive Ping/Pong commands. The gap in Ping/Pong was addressed in #15382. > > Thanks @lhotari reply, the two PRs mentioned here address a different issue than the one this current PR aims to resolve. The primary objective of the current PR is to resolve connection interruptions that occur in physical machine deployment environments. These interruptions stem from the fact that Bookkeeper and Broker instances are deployed on separate physical nodes, and—due to intervening firewall restrictions—rely on the operating system's default keep-alive settings, which have an excessively long timeout duration. Yes, that was a sidenot. Please check what I provided in the example. It's already possible to tune the keep-alive for BookKeeper client. In addition, you will need to anyways tune BookKeeper server separately to complete the solution. ``` "PULSAR_PREFIX_bookkeeper_tcpKeepIdle": "300" "PULSAR_PREFIX_bookkeeper_tcpKeepIntvl": "60" "PULSAR_PREFIX_bookkeeper_tcpKeepCnt": "5" ``` The `bookkeeper_` prefix solution was added in #9232 and documented in #15818. Please read my comments in the review. -- 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]
