You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/05/07 01:59:37 UTC

[GitHub] [shardingsphere] wsg96321 commented on issue #17308: connection leak for sharding proxy

wsg96321 commented on issue #17308:
URL: https://github.com/apache/shardingsphere/issues/17308#issuecomment-1120108800

   > Hi @wsg96321 Your server config is not the 5.x style. Could you `cat server.yaml`? You may refer to the following links for new props format:
   > 
   > https://github.com/apache/shardingsphere/blob/1699736d88db8c388413229d179eeae3da705a8b/shardingsphere-proxy/shardingsphere-proxy-bootstrap/src/main/resources/conf/server.yaml#L64-L85
   > 
   > The WARN log `An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.` usually doesn't matter.
   
   Hi, I konw this config different, but thanks alot . The reason that I show this config because I just `cat` the file of the sharding proxy which running with `File mode` , then it flush config in file. Maybe it is right. 
   
   The function of this script is just connect a sharding proxy with port(8777,default is 3307) by `mysql client` without interactive for 3 seconds .It doesn't matter for this script , just for a test . The important thing is that it produce too much `TIME_WAIT` connection , and when it's count reach 30~50, the connection will block and can't get a new connection.  Is there any better suggestion or direction? 


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org