You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brpc.apache.org by GitBox <gi...@apache.org> on 2019/04/16 08:14:40 UTC

[GitHub] [incubator-brpc] lingbin opened a new issue #731: A question about supporting TCP keepalive

lingbin opened a new issue #731: A question about supporting TCP keepalive
URL: https://github.com/apache/incubator-brpc/issues/731
 
 
   In the current implementation, the parameter that sets the `TCP keepalive` is not found. 
   
   The problem is that if the client is abnormally down (such as restarting after power failure), the server may have a large number of semi-connected states, that is, The client side can't see these connections (`netstat -apno`), but it still maintains a large number of `ESTABLISHED` status links on the server side.
   At the same time, since linux does not open keepalive by default, if these connections have no data transmission, then it will always exist, and it will consume the resources of the server. And if the server side has some resource restrictions (such as limiting the total number of fd), the system will face the problem of service failure.
   
   Therefore, I feel that Brpc as an rpc library should be able to allow `TCP keepalive` to be manually enabled in the program.
   
   If there is no other special consideration in the Brpc, I can submit a PR

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org