You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by "Guocheng Zhang (Jira)" <ji...@apache.org> on 2020/10/28 02:03:00 UTC

[jira] [Assigned] (TUBEMQ-386) Add the operation of automatic reload configuration

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

Guocheng Zhang reassigned TUBEMQ-386:
-------------------------------------

    Assignee: Guocheng Zhang

> Add the operation of automatic reload configuration
> ---------------------------------------------------
>
>                 Key: TUBEMQ-386
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-386
>             Project: Apache TubeMQ
>          Issue Type: Improvement
>            Reporter: Guocheng Zhang
>            Assignee: Guocheng Zhang
>            Priority: Major
>
> At present, the reload operation is executed serially: if there are multiple configurations change, the effective time of the change will be relatively long due to the serial operation of the interface; at the same time, the reload operation requires external batch loading according to the current cluster reload status, and these settings are aggravated considering the complexity of interface usage. so I consider making the following adjustments:
> 1. The reload operation is changed to task submission mode. After receiving the task, the Master returns a task ID to the caller; the caller queries the task completion status through the task ID;
> 2. The Master controls the batches loaded and the number of each load; and periodically records the execution results of reload in the task ID.



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