Replica Set Member States副本集成员状态

Core States核心状态

PRIMARY

Members in PRIMARY state accept write operations. 处于PRIMARY状态的成员接受写操作。A replica set has at most one primary at a time. 复制副本集一次最多有一个主副本。[1] A SECONDARY member becomes primary after an election. SECONDARY成员在选举后成为主要成员。Members in the PRIMARY state are eligible to vote.PRIMARY状态的成员有资格投票。

SECONDARY

Members in SECONDARY state replicate the primary's data set and can be configured to accept read operations. 处于SECONDARY状态的成员复制主数据集，并且可以配置为接受读取操作。Secondaries are eligible to vote in elections, and may be elected to the PRIMARY state if the primary becomes unavailable.secondary有资格在选举中投票，如果primary变成不可用，他们可以被选入PRIMARY状态。

ARBITER

Members in ARBITER state do not replicate data or accept write operations. 处于ARBITER状态的成员不复制数据或接受写操作。They are eligible to vote, and exist solely to break a tie during elections. 他们有资格投票，而存在只是为了在选举中打破平局。Replica sets should only have a member in the ARBITER state if the set would otherwise have an even number of voting members, and could suffer from tied elections. 如果副本集的投票成员数为偶数，并且可能会遭遇平局选举，那么副本集应该只有一个处于ARBITER状态的成员。There should only be at most one arbiter configured in any replica set. For considerations when using an arbiter, see Replica Set Arbiter.在任何副本集中最多只能配置一个仲裁器。有关使用仲裁器时的注意事项，请参阅副本集仲裁器。

See Replica Set Members for more information on core states.有关核心状态的详细信息，请参阅副本集成员。

Other States其它状态

STARTUP

Each member of a replica set starts up in STARTUP state. 复制副本集的每个成员都以STARTUP状态启动。mongod then loads that member's replica set configuration, and transitions the member's state to STARTUP2 or ARBITER. mongod然后加载该成员的副本集配置，并将该成员的状态转换为STARTUP2或ARBITER。Members in STARTUP are not eligible to vote, as they are not yet a recognized member of any replica set.STARTUP中的成员没有资格投票，因为他们还不是任何副本集的公认成员。

STARTUP2

Changed in version 5.0.5.0版更改。

Each data-bearing member of a replica set enters the STARTUP2 state as soon as mongod finishes loading that member's configuration.一旦mongod完成加载副本集的每个数据承载成员的配置，该成员就会进入STARTUP2状态。

The member then decides whether or not to undertake an initial sync. 然后，成员决定是否进行初始同步。If a member begins an initial sync, the member remains in STARTUP2 until all data is copied and all indexes are built. 如果某个成员开始初始同步，则该成员将保留在STARTUP2中，直到复制了所有数据并建立了所有索引。Afterwards, the member transitions to RECOVERING.然后，成员转换到RECOVERING。

Newly-added members in STARTUP2 are not eligible to vote and cannot be elected during the initial sync process. STARTUP2中新添加的成员没有资格投票，并且在初始同步过程中无法当选。Prior to MongoDB 5.0, members in STARTUP2 were eligible to vote.在MongoDB 5.0之前，STARTUP2中的成员有资格投票。

RECOVERING

A member of a replica set enters RECOVERING state when it is not ready to accept reads. 副本集的成员在未准备好接受读取时进入RECOVERING状态。The RECOVERING state can occur during normal operation, and doesn't necessarily reflect an error condition. RECOVERING状态可能发生在正常操作期间，并不一定反映错误情况。Members in the RECOVERING state are eligible to vote in elections, but are not eligible to enter the PRIMARY state.RECOVERING状态的成员有资格在选举中投票，但没有资格进入PRIMARY状态。

A member transitions from RECOVERING to SECONDARY after replicating enough data to guarantee a consistent view of the data for client reads. 在复制足够的数据以保证客户端读取数据的一致性后，成员从RECOVERING转换为SECONDARY。The only difference between RECOVERING and SECONDARY states is that RECOVERING prohibits client reads and SECONDARY permits them. RECOVERING和SECONDARY状态之间的唯一区别是，RECOVERING禁止客户端读取，SECONDARY允许客户端读取。SECONDARY state does not guarantee anything about the staleness of the data with respect to the primary.state并不保证数据相对于主数据的陈旧性。

Due to overload, a secondary may fall far enough behind the other members of the replica set such that it may need to resync with the rest of the set. 由于过载，secondary可能远远落后于副本集的其他成员，因此可能需要与副本集的其余成员重新同步。When this happens, the member enters the RECOVERING state and requires manual intervention.发生这种情况时，成员将进入RECOVERING状态，并需要手动干预。

ROLLBACK

Whenever the replica set replaces a primary in an election, the old primary may contain documents that did not replicate to the secondary members. 每当复制集在选举中替换primary时，旧的主成员可能包含未复制到secondary成员的文档。In this case, the old primary member reverts those writes. During rollback, the member will have ROLLBACK state. 在这种情况下，旧的主要成员会恢复这些写入。在回滚期间，成员将处于ROLLBACK状态。Members in the ROLLBACK state are eligible to vote in elections.ROLLBACK状态的成员有资格在选举中投票。

Starting in version 4.2, MongoDB kills all in-progress user operations when a member enters the ROLLBACK state.从4.2版本开始，当成员进入ROLLBACK状态时，MongoDB会终止所有正在进行的用户操作。

Error States错误状态

Members in any error state can't vote.任何错误状态的成员都不能投票。

UNKNOWN

Members that have never communicated status information to the replica set are in the UNKNOWN state.从未向副本集传递过状态信息的成员处于UNKNOWN状态。

DOWN

Members that lose their connection to the replica set are seen as DOWN by the remaining members of the set.丢失与副本集连接的成员会被副本集的其余成员视为DOWN。

REMOVED

Members that are removed from the replica set enter the REMOVED state. 从副本集中删除的成员将进入REMOVED状态。When members enter the REMOVED state, the logs will mark this event with a replSet REMOVED message entry.当成员进入REMOVED状态时，日志将使用replSet REMOVED消息条目标记此事件。