복제본 세트 노드 상태.

핵심 상태

PRIMARY

PRIMARY상태 의 멤버는 쓰기 (write) 작업을 허용합니다. 복제본 세트 한 번에 최대 하나 프라이머리 있습니다. [1]SECONDARY회원이 투표 후 프라이머리 됩니다. PRIMARY상태 회원은 투표할 수 있습니다.

SECONDARY

Members in SECONDARY state replicate the primary's data set and can be configured to accept read operations. Secondaries are eligible to vote in elections, and may be elected to the PRIMARY state if the primary becomes unavailable.

ARBITER

Members in ARBITER state do not replicate data or accept write operations. 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. There should only be at most one arbiter configured in any replica set. For considerations when using an arbiter, see Replica Set Arbiter.

코어 상태에 대한 자세한 내용은 Replica Set Members를 참조하십시오.

기타 주

STARTUP

Each member of a replica set starts up in STARTUP state. mongod then loads that member's replica set configuration, and transitions the member's state to STARTUP2 or ARBITER. Members in STARTUP are not eligible to vote, as they are not yet a recognized member of any replica set.

STARTUP2

버전 5.0에서 변경되었습니다.

Each data-bearing member of a replica set enters the STARTUP2 state as soon as mongod finishes loading that member's configuration.

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. Afterwards, the member transitions to RECOVERING.

에 새로 추가된 멤버는 투표할 수 없으며 초기 동기화 프로세스 중에 선출될 수 없습니다.STARTUP2 MongoDB 5 이전에는.0 의 회원만 STARTUP2 투표할 수 있었습니다.

RECOVERING

A member of a replica set enters RECOVERING state when it is not ready to accept reads. The RECOVERING state can occur during normal operation, and doesn't necessarily reflect an error condition. Members in the RECOVERING state are eligible to vote in elections, but are not eligible to enter the PRIMARY state.

A member transitions from RECOVERING to SECONDARY after replicating enough data to guarantee a consistent view of the data for client reads. The only difference between RECOVERING and SECONDARY states is that RECOVERING prohibits client reads and SECONDARY permits them. SECONDARY state does not guarantee anything about the staleness of the data with respect to the primary.

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. When this happens, the member enters the RECOVERING state and requires manual intervention.

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. In this case, the old primary member reverts those writes. During rollback, the member will have ROLLBACK state. Members in the ROLLBACK state are eligible to vote in elections.

Starting in version 4.2, MongoDB kills all in-progress user operations when a member enters the ROLLBACK state.

오류 상태

오류 상태의 회원은 투표할 수 없습니다.

UNKNOWN

Members that have never communicated status information to the replica set are in the UNKNOWN state.

DOWN

Members that lose their connection to the replica set are seen as DOWN by the remaining members of the set.

REMOVED

Members that are removed from the replica set enter the REMOVED state. When members enter the REMOVED state, the logs will mark this event with a replSet REMOVED message entry.