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:07:01 UTC

[jira] [Updated] (INLONG-489) Add the maximum message length parameter setting

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

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

> Add the maximum message length parameter setting
> ------------------------------------------------
>
>                 Key: INLONG-489
>                 URL: https://issues.apache.org/jira/browse/INLONG-489
>             Project: Apache InLong
>          Issue Type: Improvement
>            Reporter: Guocheng Zhang
>            Assignee: Guocheng Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.8.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> At present, the maximum packet length of a message is set  through the TBaseConstants.META_MAX_MESSAGEG_DATA_SIZE and and the value can not be adjusted according to the needs during the running period. In an environment that exceeds the specified package length, we have to modify the value and recompile and publish the whole package, which brings trouble to the system operation and maintenance. If we can set the value according to the dynamically configurable topic, the operation and maintenance management of the system will become very simple



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