wenbingshen opened a new pull request, #3951: URL: https://github.com/apache/bookkeeper/pull/3951
### Motivation Related to this PR #3913, I noticed that the bookkeeper client often needs to maintain a permanent long connection with the bookie server that has established a connection. I guess the reason is that the creation of ensemble is based on the polling selection of all bookie nodes. Long-running services are bound to Keep in touch with all bookie servers repeatedly. Permanent long connections, especially when the client and server do not have any read-write operations, are a waste of resources (such as server-side file handles, resources occupied by socket creation internal objects, possible memory leaks). When the `AutoRecovery` service runs for a long time, its detection task will generally occur once every 1 day, 7 days, or even longer. Once the connection is established with all bookie servers, it will not actively release the connection unless some abnormality occurs. ### Changes For this reason, I want to add a maximum idle connection time on the client side to actively close some network connections that have not performed read-write operations for a long time. This future is disabled by default. New configuration: `clientMaxIdleConnectionsMinutes`, Default is -1 (disabled) -- 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]
