Cassandra如何选择协调器节点和复制节点？ [英] how Cassandra chooses the coordinator node and the replication nodes?

问题描述

Cassandra客户端如何选择协调器节点？
是协调节点在复制前存储客户端发送的数据吗？

How the Cassandra client chooses the coordinator node? is the coordinator node stores the data sent by the client before replicating?

推荐答案

协调节点通常由一种考虑网络距离的算法。任何节点都可以充当协调器，并且首先将请求发送到您的驱动程序知道的节点。但是一旦连接并了解了群集的拓扑，它就可能会变成更紧密的协调器。

The coordinator node is typically chosen by an algorithm which takes "network distance" into account. Any node can act as the coordinator, and at first requests will be sent to the nodes which your driver knows about. But once it connects and understands the topology of your cluster, it may change to a "closer" coordinator.

如果协调器仅在本地存储数据（写操作）最终成为负责数据令牌范围的节点之一。

The coordinator only stores data locally (on a write) if it ends up being one of the nodes responsible for the data's token range.

这篇关于Cassandra如何选择协调器节点和复制节点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！