[Proxy] Pulsar Handshake was not completed within timeout, Proxy stops working for proxying Broker connections while Admin API proxying keeps working ,
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
**Describe the bug**
Pulsar Proxy can get into a state where it stops proxying Broker connections while Admin API proxying keeps working.
The proxy logs are filled with this type of warnings:
but directly connect pulsar-broker is normally,
```
13:13:09.996 [pulsar-proxy-io-2-1] WARN org.apache.pulsar.common.protocol.PulsarHandler - [[id: 0x83e12747, L:/ip:port - R:/ip:port]] Pulsar Handshake was not completed within timeout, closing connection
```
and back to normally after restart proxy.
i saw the similar issue:
https://github.com/apache/pulsar/issues/14075
https://github.com/apache/pulsar/pull/14078
**To Reproduce**
The steps to reproduce are not known.
Contributor guide
Research direction
Start by reviewing the related issue #14075 and pull request #14078, then examine the reported Pulsar Proxy warning about the handshake timeout. The reproduction steps are currently unknown, so first establish how Broker proxying can stop while Admin API proxying continues. Done means the failure is reproducible and the proxy no longer remains unable to proxy Broker connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100