[SERVER-9245] Separate oplog per database Created: 04/Apr/13  Updated: 10/Dec/14  Resolved: 04/Apr/13

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

Type: New Feature Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-5723 separate journaling per database Closed
Participants:

 Description   

Would give us wins in terms of concurrency as well as operations (for example, backing up/restoring a single database). Also opens to door for even more interesting replication layouts, like you could have a secondary replicating one database from one server, and a different database from a different server.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 04/Apr/13 ]

don't think this is something we'd consider, lots of other ways to increase concurrency around the oplog, and limits a lot of other options.

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