Couchbase 中的主节点是什么？
What is the Master node in Couchbase?
在 Couchbase 文档中：https://developer.couchbase.com/documentation/server/current/concepts/distributed-data-management.html
There is no concept of master nodes, slave nodes, config nodes, name nodes, head nodes, etc, and all the software loaded on each node is identical
但在我的日志中，我收到了 post 中的消息：
https://forums.couchbase.com/t/havent-heard-from-a-higher-priority-node-or-a-master-so-im-taking-over/5924
Haven't heard from a higher priority node or a master, so I'm taking over. mb_master 000 ns_1@10.200.0.10 1:07:38 AM Tue Feb 7, 2017
和
Somebody thinks we're master. Not forcing mastership takover over ourselves mb_master 000 ns_1@10.200.0.10 1:07:28 AM Tue Feb 7, 2017
我很难找到 master 做什么，因为任何关于 master 的搜索都会导致 couchbase 没有主节点的评论。
错误消息似乎源自集群管理，看起来应该像 this (I didn't manage to find the Couchbase implementation of it). The link points to the implementation of membase which is the predecessor of Couchbase。
虽然在 Couchbase 中所有节点都是平等的，但是当有一些数据重新分配时，不是这种情况。正如本 document 中详细描述的那样，选择了一个 master 来管理重新分发。您收到的日志消息就是由此过程引起的。
集群管理器中的主节点也称为编排器。
直接来自 Couchbase Server 4.6 文档，https://developer.couchbase.com/documentation/server/4.6/concepts/distributed-data-management.html
Although each node runs its own local Cluster Manager, there is only
one node chosen from among them, called the orchestrator, that
supervises the cluster at a given point in time. The orchestrator
maintains the authoritative copy of the cluster configuration, and
performs the necessary node management functions to avoid any
conflicts from multiple nodes interacting. If a node becomes
unresponsive for any reason, the orchestrator notifies the other nodes
in the cluster and promotes the relevant replicas to active status.
This process is called failover, and it can be done automatically or
manually. If the orchestrator fails or loses communication with the
cluster for any reason, the remaining nodes detect the failure when
they stop receiving its heartbeat, so they immediately elect a new
orchestrator. This is done immediately and is transparent to the
operations of the cluster.
在 Couchbase 文档中：https://developer.couchbase.com/documentation/server/current/concepts/distributed-data-management.html
There is no concept of master nodes, slave nodes, config nodes, name nodes, head nodes, etc, and all the software loaded on each node is identical
但在我的日志中，我收到了 post 中的消息： https://forums.couchbase.com/t/havent-heard-from-a-higher-priority-node-or-a-master-so-im-taking-over/5924
Haven't heard from a higher priority node or a master, so I'm taking over. mb_master 000 ns_1@10.200.0.10 1:07:38 AM Tue Feb 7, 2017
和
Somebody thinks we're master. Not forcing mastership takover over ourselves mb_master 000 ns_1@10.200.0.10 1:07:28 AM Tue Feb 7, 2017
我很难找到 master 做什么，因为任何关于 master 的搜索都会导致 couchbase 没有主节点的评论。
错误消息似乎源自集群管理，看起来应该像 this (I didn't manage to find the Couchbase implementation of it). The link points to the implementation of membase which is the predecessor of Couchbase。
虽然在 Couchbase 中所有节点都是平等的，但是当有一些数据重新分配时，不是这种情况。正如本 document 中详细描述的那样，选择了一个 master 来管理重新分发。您收到的日志消息就是由此过程引起的。
集群管理器中的主节点也称为编排器。
直接来自 Couchbase Server 4.6 文档，https://developer.couchbase.com/documentation/server/4.6/concepts/distributed-data-management.html
Although each node runs its own local Cluster Manager, there is only one node chosen from among them, called the orchestrator, that supervises the cluster at a given point in time. The orchestrator maintains the authoritative copy of the cluster configuration, and performs the necessary node management functions to avoid any conflicts from multiple nodes interacting. If a node becomes unresponsive for any reason, the orchestrator notifies the other nodes in the cluster and promotes the relevant replicas to active status. This process is called failover, and it can be done automatically or manually. If the orchestrator fails or loses communication with the cluster for any reason, the remaining nodes detect the failure when they stop receiving its heartbeat, so they immediately elect a new orchestrator. This is done immediately and is transparent to the operations of the cluster.