[Enhancement] The client reports heartbeats to the broker using an asynchronous method.

[chenyi19851209]

Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

I hope to change the way the client reports heartbeats to the broker to an asynchronous method. The scenarios I am considering are as follows: During batch publishing for the broker or IDC (Internet Data Center) network disconnection drills, the client synchronously reports heartbeats to the broker that has abnormally disconnected. This causes continuous blocking and waiting timeouts in heartbeat reporting, which in turn leads to significant delays in the client's heartbeat reporting to the normally connected brokers. Changing to asynchronous heartbeat reporting can prevent the abnormal broker from blocking the heartbeat reporting to the normal brokers.

Motivation

Avoid heartbeat blocking in scenarios such as batch publish and restarts of the broker, as well as IDC (Internet Data Center) anomaly drills.

Describe the Solution You'd Like

The method of the client sending heartbeats to a single broker is changed to an asynchronous sending method（InvokeAsync）

Describe Alternatives You've Considered

none

Additional Context

No response

[chenyi19851209]

Specific code location

[yx9o]

The broker will map some data when processing the heartbeat. Will this cause the data obtained by other interfaces to have time differences or be incorrect?

[chenyi19851209]

Currently, I see that there are three locations on the broker server where a map is maintained to process heartbeat data. They are all concurrent maps, and not require the order of processing. The expected asynchronous reporting of heartbeats can accelerate the acquisition of correct data and will not lead to worse results