News for hackers. Stuff that matters.
Re:InfluxDB Clustering Design – Neither CP or AP by pauldix on Wednesday June 03, 2015 @10:13PM (#9657059)
They could have an out of date view of the cluster. Like which databases exist, or which servers exist.

However, those cases are fine. If a database was created and a server doesn't have a copy of it. When a write comes in it'll be a cache miss so it'll hit the Raft system to get the info.

In the case of a new server joining the cluster, it won't get new data assigned until a shard group gets created and a shard gets assigned to it. When a write comes in if a node doesn't have a shard group for that time range, it'll all out to the Raft system to get the information.

So yes, it's possible for some servers to have a stale view of this cluster metadata, but we work around it by having them request the information on demand and periodically refresh the entire thing.

Re:InfluxDB Clustering Design – Neither CP or AP by schmichael on Wednesday June 03, 2015 @10:30PM (#9657115)
Thanks for the more detailed explanation! Really looking forward to further posts -- not to mention 0.9!