You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by GitBox <gi...@apache.org> on 2021/07/28 12:15:41 UTC

[GitHub] [incubator-inlong] dockerzhang opened a new issue #1180: [INLONG-591] ZkOffsetStorage module improvements

dockerzhang opened a new issue #1180:
URL: https://github.com/apache/incubator-inlong/issues/1180


   <p>Based on the consideration of removing the BDB, we will extract the metadata and the active/standby keep-alive logic (completed by issue <a href="https://issues.apache.org/jira/browse/TUBEMQ-570" class="external-link" rel="nofollow">https://issues.apache.org/jira/browse/TUBEMQ-570</a>), and then migrate to Zookeeper-based metadata storage and active/standby keep-alive (completed by issue <a href="https://issues.apache.org/jira/browse/TUBEMQ-567" class="external-link" rel="nofollow">https://issues.apache.org/jira/browse/TUBEMQ-567</a>).</p>
   
   <p>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 <a href="https://issues.apache.org/jira/browse/INLONG-570" title="Optimizing the implementations of HTTP API for Master" class="issue-link" data-issue-key="INLONG-570">TUBEMQ-570</a>)</p>
   
   <p>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.</p>
   <i>JIRA link - <a href="https://issues.apache.org/jira/browse/INLONG-591">[INLONG-591]</a> created by gosonzhang</i>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org