GBM-tamerm opened a new issue #14826:
URL: https://github.com/apache/pulsar/issues/14826
**Describe the bug**
e saw strange behaviour , as broker stopped accepting connections and
clients start receiving different exceptions such as : Connection Already
Closed , Topic not available ,
exceptions.
The broker java process itself is up and running, but curl http ports such
as curl broker metrics stop return anything.
It is only works when we restart the broker again
So it seems as connection pool issue or leak as it keeps alive speically we
can some logs entries as below
[pulsar-client-io-1-1] INFO org.apache.pulsar.client.impl.ConnectionPool -
[[id: 0x15a65d4f, L:/10.244.63.22:36068 - xxxxx:6651]] Connected to server
Killed
**To Reproduce**
I was able to reproduce the issue by a simple java program which keep
looping while opening new
socket to the broker port without closing the socket on every loop. So
after a while the clients start to get that connection already closed
exceptions and others.
**Expected behavior**
Broker should not freeze , generate meaningful exception which disconnecting
bad clients
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: Linux VM
- 6 brokers
- 6 bookies
- 5 ZK
**Additional context**
No k8 deployment , and client accessing brokers DNS directly without Pulsar
proxy.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
