ltamber opened a new issue #6319: [pulsar client] partitioned topic cause 
connection leak when connection pool disable pooling
URL: https://github.com/apache/pulsar/issues/6319
 
 
   **Describe the bug**
   when use partitioned topic, the connection from client to discovery service 
will grow up and keep alive util application shut down.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. we used pulsar-perf, command is: ./bin/pulsar-perf consume -n 6 -c 0 -u 
pulsar://x.x.x.x:6660,x.x.x.x:6660 -s sub-1 -st Failover 
tenantTest/namespaceTest/partitiontopic2
   2. then netstat -anp | grep 6660 | wc -l, the connection number will 
increasing slowly
   
   **Expected behavior**
   if we disable pooling, the connection should close when we done our lookup.
   
   
   **Screenshots**
   
![image](https://user-images.githubusercontent.com/5679413/74398752-9fe41b00-4e53-11ea-9dba-74ded0371c22.png)
   
   **Additional context**
   there is a timer in partition topic client will autoUpdatePartitions, every 
getPartitionsForTopic will create a new connection and won't close it
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to