[
https://issues.apache.org/jira/browse/IOTDB-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109494#comment-17109494
]
Giorgio Zoppi commented on IOTDB-68:
------------------------------------
This part is typically hard to write correctly. You can use:
* [https://etcd.io/]
* [https://github.com/hashicorp/consul]
A node could rely on third party service who has the only respisbility for
leader election.
https://godoc.org/github.com/coreos/etcd/clientv3/concurrency#Election.Leader
> IoTDB supports distributed version
> ----------------------------------
>
> Key: IOTDB-68
> URL: https://issues.apache.org/jira/browse/IOTDB-68
> Project: Apache IoTDB
> Issue Type: New Feature
> Reporter: XuYi
> Priority: Major
> Labels: features, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hi, IoTDB only supports stand-alone version now. We plan to develop
> distributed version in next two months.
> We initially decided to use the master-slave architecture. The master node is
> responsible for processing read and write requests, and the slave node is
> responsible for processing read-only requests as a copy.
> In terms of implementation, we currently intend to use the raft protocol to
> ensure the data consistency of each replica node.
> If you have any suggestion, please comment below or send an email to our
> mailing list([email protected]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
