[DOCS-13688] State transition description not correct for Arbiters Created: 04/Jun/20 Updated: 30/Oct/23 Due: 05/Jun/20 Resolved: 04/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Nic Cottrell | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 3 years, 35 weeks, 6 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
DescriptionLink: https://docs.mongodb.com/manual/reference/replica-states/index.html#replstate.STARTUP2 This states: > Each member of a replica set enters the STARTUP2 state as soon as mongod finishes loading that member’s configuration, at which time it becomes an active member of the replica set and is eligible to vote. However arbiters seem to go straight from STARTUP->ARBITER as per these log lines:
Tested in v4.2 but probably applies to all recent versions. Maybe a change to "Each data-bearing member of a replica set enters..." would be sufficient. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 04/Jun/20 ] |
|
Author: {'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 04/Jun/20 ] |
|
Author: {'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Kay Kim (Inactive) [ 04/Jun/20 ] |
|
Checked through v3.6. [v4.0] [v3.6] |