[GitHub] [pulsar] GBM-tamerm edited a comment on issue #14826: Too many TCP Connections are in CLOSE_WAIT status freeze broker v 2.7.4

[GitBox <gi...@apache.org>]

GBM-tamerm edited a comment on issue #14826:
URL: https://github.com/apache/pulsar/issues/14826#issuecomment-1078832791


   Hi Lari ,
   
   I did your suggestions and did not resolve the issue , broker still freeze after a while 
   I think the potential cause for that is most likely a deadlock or racing between broker and bookie clients connections ,i updated the issue description to reflect more details
   Too many TCP Connections are in CLOSE_WAIT status in a Pulsar broker causing Disconnection Exceptions and Connection Already Close exceptions in pulsar clients
   
   As the majority of the close_ wait connections between broker and bookies, it indicate deadlock /race is happening
   
   attached the jstack that shows the deadlock
   [jstack_12.txt](https://github.com/apache/pulsar/files/8403100/jstack_12.txt)
   
   https://jstack.review?https://gist.github.com/GBM-tamerm/a29b793db94702ea58da449927938cad
   
   


-- 
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: commits-unsubscribe@pulsar.apache.org

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