You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@inlong.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/07/28 12:14:01 UTC

[jira] [Updated] (INLONG-313) Broker heartbeat performance issues

     [ https://issues.apache.org/jira/browse/INLONG-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated INLONG-313:
----------------------------------
    Labels: pull-request-available  (was: )

>  Broker heartbeat performance issues
> ------------------------------------
>
>                 Key: INLONG-313
>                 URL: https://issues.apache.org/jira/browse/INLONG-313
>             Project: Apache InLong
>          Issue Type: Improvement
>          Components: inlong-tubemq
>            Reporter: Haiji Li
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Broker heartbeat performance issues
> At present, Broker needs to report heartbeats regularly. In the case of large batch requests, when the CPU performance of the client and server is very high, the heartbeat report is not timely, and there is a high probability that the heartbeat report fails, causing the client to disconnect.
> At the optimization point, the data packet request of the client can be regarded as the heartbeat data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)