Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- tertiary

Assigned Teams:

Replication
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

It would be nice to be able to have a master/slave setup where the master is actually a replica set and the slaves are just that, slaves. This is handy for when there are more than 12 nodes and when the slaves will never become master.

is duplicated by

SERVER-12023 allow non-voting p=0 nodes to not require connectivity to other non-voting p=0 nodes

Closed

SERVER-8900 Increasing the max size of replica sets with non-voting members

Closed

SERVER-27169 Maximum number of members in replica set should not be limited to 50

Closed

related to

SERVER-7156 w:majority issues with votes

Closed

SERVER-7555 Do not veto election based on stale data for down members

Closed

SERVER-14598 Slaves should handshake all their chained members at once

Closed

SERVER-26114 Increase maximum number of replica set members from 50 to 100

Backlog

SERVER-15060 Raise maximum number of nodes in a replica set

Closed

(3 related to)

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Kimo Rosenbaum
Participants:: [DO NOT USE] Backlog - Replication Team, Kimo Rosenbaum, Steven Vannelli
Votes:: 16 Vote for this issue
Watchers:: 40 Start watching this issue

Created:: May 16 2011 10:39:56 PM UTC
Updated:: Dec 06 2022 05:43:40 AM UTC
Resolved:: Oct 07 2019 08:59:13 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates