[jira] [Assigned] (IOTDB-567) Apache IoTDB's Peer Tracker for The Raft Protocol [distributed]
[ https://issues.apache.org/jira/browse/IOTDB-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tan xinyu reassigned IOTDB-567: --- Assignee: Tan xinyu > Apache IoTDB's Peer Tracker for The Raft Protocol [distributed] > --- > > Key: IOTDB-567 > URL: https://issues.apache.org/jira/browse/IOTDB-567 > Project: Apache IoTDB > Issue Type: Task > Components: Core/Cluster >Reporter: Xiangdong Huang >Assignee: Tan xinyu >Priority: Major > Labels: IoTDB, gsoc2020, mentor > > IoTDB is a highly efficient time-series database, which supports high-speed > query process, including aggregation query. > Currently, clustered IoTDB is under close development. It now supports leader > election, log replication, cluster membership change, and log compaction. We > are testing and optimizing these features these days. > However, we have not yet implemented log status tracking for peers, which > leads to the fact that when sending the logs, the logs required by a peer may > not be immediately sent correctly, resulting in wasted bandwidth and possible > errors. > So there are two improvements about peer tracker need to be done: > 1.implement a peer tracker to track follower's log status. You can borrow > from other projects or design your own, as long as it's right. > 2.you should also dynamically maintain the peer tracker on the current design > and handle possible conflicting inconsistencies, this requires a little > understanding of IoTDB’s raft log module. > This proposal is mainly for implementing and maintaining a peer tracker in > clustered IoTDB. > It is necessary for you to understand that correctness is the most important > thing. > You should know: > - IoTDB cluster structure > - IoTDB raft RPC module > - IoTDB raft log module > - Raft > - Java > difficulty: Major > Mentor: > jt2594...@163.com, h...@apache.org > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-567) Apache IoTDB's Peer Tracker for The Raft Protocol [distributed]
[ https://issues.apache.org/jira/browse/IOTDB-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tan xinyu reassigned IOTDB-567: --- Assignee: Tan xinyu > Apache IoTDB's Peer Tracker for The Raft Protocol [distributed] > --- > > Key: IOTDB-567 > URL: https://issues.apache.org/jira/browse/IOTDB-567 > Project: Apache IoTDB > Issue Type: Task > Components: Core/Cluster >Reporter: Xiangdong Huang >Assignee: Tan xinyu >Priority: Major > Labels: IoTDB, gsoc2020, mentor > > IoTDB is a highly efficient time-series database, which supports high-speed > query process, including aggregation query. > Currently, clustered IoTDB is under close development. It now supports leader > election, log replication, cluster membership change, and log compaction. We > are testing and optimizing these features these days. > However, we have not yet implemented log status tracking for peers, which > leads to the fact that when sending the logs, the logs required by a peer may > not be immediately sent correctly, resulting in wasted bandwidth and possible > errors. > So there are two improvements about peer tracker need to be done: > 1.implement a peer tracker to track follower's log status. You can borrow > from other projects or design your own, as long as it's right. > 2.you should also dynamically maintain the peer tracker on the current design > and handle possible conflicting inconsistencies, this requires a little > understanding of IoTDB’s raft log module. > This proposal is mainly for implementing and maintaining a peer tracker in > clustered IoTDB. > It is necessary for you to understand that correctness is the most important > thing. > You should know: > - IoTDB cluster structure > - IoTDB raft RPC module > - IoTDB raft log module > - Raft > - Java > difficulty: Major > Mentor: > jt2594...@163.com, h...@apache.org > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
