[jira] [Updated] (INLONG-591) ZkOffsetStorage module improvements

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

> ZkOffsetStorage module improvements
> -----------------------------------
>
>                 Key: INLONG-591
>                 URL: https://issues.apache.org/jira/browse/INLONG-591
>             Project: Apache InLong
>          Issue Type: Improvement
>          Components: inlong-tubemq
>            Reporter: Guocheng Zhang
>            Priority: Normal
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Based on the consideration of removing the BDB, we will extract the metadata and the active/standby keep-alive logic (completed by issue https://issues.apache.org/jira/browse/TUBEMQ-570), and then migrate to Zookeeper-based metadata storage and active/standby keep-alive (completed by issue https://issues.apache.org/jira/browse/TUBEMQ-567).
> The Zk interaction logic of TubeMQ adopts the early implementation of HBase. Considering the cleanliness of the code, users who have a deeper understanding of ZK interaction can try to reconstruct this piece of business logic to provide better metadata storage and master Implementation of the interface for standby switching (the relevant interface abstraction is defined on the metamanage module of the branch TUBEMQ-570)
> This part is very difficult and requires experienced students to analyze and check it. Before actually doing it, many discussions are needed to confirm whether there is a better approach.



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