brain and lose data?
>
>
>
> ____
> From: Julian Feinauer
> Sent: Sunday, March 31, 2019 11:34 AM
> To: dev@iotdb.apache.org
> Subject: Re: IoTDB supports distributed version
>
> Hi Felix,
>
> could y
: Julian Feinauer
Sent: Sunday, March 31, 2019 11:34 AM
To: dev@iotdb.apache.org
Subject: Re: IoTDB supports distributed version
Hi Felix,
could you elaborate a bit on your use cases?
I am a bit unsure about the consistency, so it would be interesting to hear
where you see the important points.
Thanks
the strong consistency
option.
(Very cool discussion!)
From: Julian Feinauer
Sent: Thursday, March 28, 2019 1:10 AM
To: dev@iotdb.apache.org
Subject: Re: IoTDB supports distributed version
Hi,
this is a very i
Hi,
this is a very interesting (and important) question.
I think we should really consider what we can skip (from an application
perspective) and what to keep.
Perhaps a Token Ring architecture like Cassandra uses could also be a good fit,
if we hash on the device id or something.
At least in
yep, I think the cluster is in P2P mode when they startup. Then a leader
election algorithm will change the cluster into the M/S mode (RAFT
algorithm is qualified). If the master is down, a new master can be elected
and lead the cluster.
By the way, we need to consider the cost of keeping strong
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
