Apache IoTDB支持的RatisConsensus和IoTConsensus的集群数据节点的容错性是多少?

huangapple go评论61阅读模式
英文:

What is the fault tolerance of cluser datanodes for RatisConsensus and IoTConsensus supported by Apache IoTDB?

问题

Apache IoTDB支持的共识协议正在学习中。我想知道当数据复制的共识协议设置为RatisConsensus时,如果集群有3个数据节点且数据副本数量为3,因为RatisConsensus具有强一致性,当其中一个数据节点出现故障时,是否无法将数据写入集群?此外,IoTConsensus(也由IoTDB支持)对于这个问题是否相同?

我查看了有关共识的官方网站,但没有回答特定数量的集群数据节点下的可用性问题。我需要一个针对这种特定情况的答案。

英文:

I am learning the consensus supported by Apache IoTDB. I wonder when the consensus protocol of data copy is set to RatisConsensus, when the cluster has 3 data nodes and the number of data copies is 3, because RatisConsensus has strong consistency, is it impossible to write data to the cluster when one of the datanodes goes wrong? Also, is IoTConsensus (also supported by IoTDB) the same for this question?

I checked the official website about consensus, but it did not answer availability under specific number of cluster datanodes. I need an answer for this specific circumstance.

答案1

得分: 0

目前,如果超过一半的数据节点正常,那么集群可以正常运行支持Apache IoTDB的三种共识协议。换句话说,如果两个节点出现故障,就无法执行写操作。然而,IoTConsensus由IoTDB自行开发,具有更高的可用性,因此在您的情况下,即使只有一个数据节点在使用IoTConsensus时仍然存活,新数据也可以插入到集群中。

英文:

At present, if more than half of the datanodes are normal, then the cluster can normally operate for the three consensus protocols supported by Apache IoTDB, that is to say, if two nodes went wrong, writing cannot be performed. However, IoTConsensus is self-developed by IoTDB and has higher availability, so in your scenario, even if only one datanode survives when using IoTConsensus, new data can also be inserted into the cluster.

huangapple
  • 本文由 发表于 2023年6月19日 10:03:02
  • 转载请务必保留本文链接:https://go.coder-hub.com/76503220.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定