[SERVER-557] replica sets Created: 20/Jan/10  Updated: 12/Jul/16  Resolved: 30/Jul/10

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 1.5.7

Type: New Feature Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Dwight Merriman
Resolution: Done Votes: 44
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-30 a slave should be able to replicate f... Closed
is depended on by SERVER-941 multiple servers per shard (WAS: use ... Closed
Related
related to SERVER-992 replciation should be rack and data c... Closed
Participants:

 Comments   
Comment by Dwight Merriman [ 30/Aug/10 ]

@frank you cannot do that yet. Although you could have local replication to a second server in the primary data center, and one remote server elsewhere today.

Comment by Frank Soetebeer [ 30/Aug/10 ]

Is datacenter awareness actually a supported feature in 1.6.1 now? If so, how would one configure MongoDB to only sync data once from the main DC to the 2nd one and distribute the changes to the other RS members in the 2nd DC only locally?

Comment by Eliot Horowitz (Inactive) [ 19/Jul/10 ]

ETA for 1.6 is end of july

Comment by Pen Fold [ 19/Jul/10 ]

Is there an ETA for a production release of Sharding (other than just release 1.6)?

Comment by Dwight Merriman [ 28/Apr/10 ]

yes - although ther'es a chance that may come in a point release shortly after first version

Comment by Leon Mergen [ 28/Apr/10 ]

Another question: will it be possible to include geographical topology of nodes with the replication acknowledgment via getlasterror? For example, being able to block until the data has been replicated to at least 1 node in a different datacenter.

Comment by Eliot Horowitz (Inactive) [ 26/Mar/10 ]

Yes - we're thinking of different ways to handle that - but its definitely something we'll be adding support for.

Comment by Leon Mergen [ 26/Mar/10 ]

Would it be possible to handle some sort of geographical location of the mongodb nodes within the replica set? This would allow us to, for example, have 2 mongodb nodes per datacenter, and when one node of the "main" datacenter fails, the other node within the same datacenter will be the preferred failover node.

Comment by Dwight Merriman [ 23/Feb/10 ]

replica sets will address many (most) limitations of replica pairs.

Generated at Thu Feb 08 02:54:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.