[SERVER-10470] per-db replication configuration / state (per-db master, etc) Created: 09/Aug/13  Updated: 10/Dec/14  Resolved: 12/Aug/13

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

Type: New Feature Priority: Minor - P4
Reporter: Ron Waldon Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: replicaset, replication, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently, each Replica Set has exactly one master at any time. Reads may be performed by slaves, but writes always go to the master.

It may be advantageous to allow this master-slave preference to be controlled per-DB. For example:

  • DB: "global"; replicaSet: no-preferred master
  • DB: "usa"; replicaSet: prefer USA-located replica members to be master
  • DB: "asia"; replicaSet: prefer Asia-located replica members to be master

This would allow a single known-working cluster to be used for multiple region-specific purposes without needing to create and maintain region-specific clusters.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 12/Aug/13 ]

I don't think db level settings for this make sense.

You can do this with sharding and 1 replica set per geography.
In that model you can even do it in 1 collection with tagged sharding.

We are working on tools to make setting that up simpler.

Note: you can run all the replica sets on the same hardware, so shouldn't be more costly.

Generated at Thu Feb 08 03:23:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.