[DOCS-6940] Member or Node Created: 08/Jan/16 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Marius il?nas | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | member, node | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
I get confused by terms in MongoDB documentation. In documentation it is mixed: sometimes a MongoDB instance is named node sometimes member. See https://docs.mongodb.org/manual/reference/replica-states/ it says ... each member of a replica set has a state that reflects... In some circumstances, two nodes in a replica set may transiently believe that they are the primary, but at most, one of them will be able to complete writes with { w: "majority" }write concern. The node that can complete { w: "majority" }writes is the current primary, and the other node is a former primary that has not yet recognized its demotion, typically due to a network partition Why documentation uses node and member not only one of them? Choose one and stick to it. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |