Hi XuYi, I like the idea but I'm unsure if I like the master / slave approach. We often deal with "Shopfloor" Scenarios where the setup for the Database is basically "MultiMaster", because we need to sync data one the one hand, but if a system goes down, everything else should keep working. Would this be possible with your approach? Something like leader re-election with Zookeper (or better Curator?). What exactly are the use cases you have in mind?
Thanks! Julian Am 28.03.19, 05:32 schrieb "徐毅" <[email protected]>: 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, which is a copy of master node is responsible for processing read-only requests. In terms of implementation, we currently intend to use the raft protocol to ensure the data consistency of each replica node. I have created an issue on jira at [1]. If you have any suggestion, please comment on jira or reply to this email. [1]. https://issues.apache.org/jira/browse/IOTDB-68 Thanks XuYi
