You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/10/29 00:15:26 UTC

[GitHub] codelipenghui opened a new issue #2876: Limit the client reconnect behavior.

codelipenghui opened a new issue #2876: Limit the client reconnect behavior.
URL: https://github.com/apache/pulsar/issues/2876
 
 
   ## Actual behavior
   
   I got some un-normal metrics in broker stats.
   
   <img width="554" alt="wechatimg101" src="https://user-images.githubusercontent.com/12592133/47623764-115d6480-db50-11e8-90fa-c7c4f31b45d0.png">
   
   Next, I check the network monitor. At that time, network is almost reach the celling.
   
   <img width="1279" alt="wechatimg111" src="https://user-images.githubusercontent.com/12592133/47623827-b0825c00-db50-11e8-8573-d45290dd2e43.png">
   
   So, I find the error log in pulsar cluster, something looks strange:
   
   ![wechatimg113](https://user-images.githubusercontent.com/12592133/47623893-4ae29f80-db51-11e8-8a85-346644fbbd34.jpeg)
   
   Than, i search the client logs in kibana:
   
   <img width="1271" alt="wechatimg143" src="https://user-images.githubusercontent.com/12592133/47623928-88dfc380-db51-11e8-8dd4-5661e6d709fe.png">
   <img width="895" alt="wechatimg144" src="https://user-images.githubusercontent.com/12592133/47623929-88dfc380-db51-11e8-9490-a30035dface1.png">
   <img width="676" alt="wechatimg145" src="https://user-images.githubusercontent.com/12592133/47623930-88dfc380-db51-11e8-9fc4-54ff1f84f349.png">
   
   Don't care about the client exception, just talk the client reconnect behavior, i think client reconnect to much and load data from bookie make the high network throughput, and for now pulsar client support updateServiceUrl() to user, this method will trigger reconnect behavior.
   
   ## conclusion
   We should limit the client reconnect behavior to avoid the high load.
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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