[Feature] Maintain heartbeat between proxy and broker
- Dominant language
- Java
- Stars
- 22.6k
- Forks
- 12k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 26
Description
### Is Your Feature Request Related to a Problem?
When the cluster traffic is not high or the cluster size is large enough, the proxy and broker only maintain the connection by sending messages or other information. There is a chance that the connection will be established only when sending or consuming. Because the broker will close the idle connection after 120 seconds.
A logic similar to the previous client is needed to send heartbeats regularly.
### Describe the Solution You'd Like
A logic similar to the previous client is needed to send heartbeats regularly.
### Describe Alternatives You've Considered
no
### Additional Context
_No response_
Contributor guide
Research direction
Trace how the proxy and broker establish and maintain connections, then compare it with the previous client's heartbeat logic mentioned in the issue. Define the regular heartbeat behavior and verify that idle connections remain usable without waiting for message or consume traffic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100