[SERVER-5761] Replicate admin database first on initial sync from master Created: 03/May/12  Updated: 15/Nov/21  Resolved: 19/Jun/17

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

Type: Improvement Priority: Major - P3
Reporter: Will Shulman Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-28151 Authentication database should be syn... Closed
Participants:

 Description   

It would be nice to replicate the admin database first when a slave does an initial sync so that the admin user collection exists on the slave early in the replication process, allowing clients to authenticate to the admin database while the sync is running. Currently, if you use -auth, clients cannot connect to new slaves until the admin database replicates, which can often take a while.



 Comments   
Comment by Eric Milkie [ 19/Jun/17 ]

We have since decided to do this work; see the linked ticket.

Comment by Alexander Ivanes [ 19/Jun/17 ]

Hello. What about monitoring system data?

We have a database named "a" with size about ~4TB. Because "initial sync" clones databases alphabetically it choose to clone it first. Monitoring data is not available until "a" clone is finished (about ~30 hours) which is very bad by my opinion.

Comment by Eric Milkie [ 10/Apr/14 ]

Clients cannot reliably read from new slaves until all the databases are replicated as part of initial sync, so I don't see a benefit in replicating the admin database first.

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