Re: [mongodb-dev] Master - Slave Replication - Initial Sync taking lot of time

150 views
Skip to first unread message

Nat

unread,
Aug 10, 2012, 11:50:01 AM8/10/12
to mongo...@googlegroups.com
How large is your database? Is there a lot of disk/network activity? Can you check rs.status() or db.printReplicationInfo() to see whether there any movement?
From: prasanna venkatesan <tele...@gmail.com>
Date: Fri, 10 Aug 2012 05:38:32 -0700 (PDT)
Subject: [mongodb-dev] Master - Slave Replication - Initial Sync taking lot of time

Hello Folks

  Probably this question has been discussed before but i could not find any of them . This is my issue

  We just need a data back up set up and hence choose to go for master slave set up and not replication . We dont want automated failover

  My master data has few hundred documents in about 4 collections . I set up a slave and initiated replication . Its been quite a while , almost 6-7 hours and the initial sync is still on . I dont see any collections in my slave database . There is no new activity in the master set up and the op long continues to be filled with new entries every 10 seconds

  Where else can i get more information . Since our data is small , i dont think the op log will ever roll over . If it is allocated the 5% of disk space ( which is default ) i guess it should be atleast a GB . 

  Any help would be appreciated

Thanks
Prasanna

--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/mongodb-dev/-/GWxlQDxvG2wJ.
To post to this group, send email to mongo...@googlegroups.com.
To unsubscribe from this group, send email to mongodb-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-dev?hl=en.

Chris Winslett

unread,
Aug 11, 2012, 5:02:12 PM8/11/12
to mongo...@googlegroups.com
Typically, the longest time during the initial sync is building indexes -- particularly if you have larger indexes.  We see 30 GB / hour data transfers on AWS -- however, building an index can take much longer.

Chris
MongoHQ

Chris Winslett

unread,
Aug 11, 2012, 5:03:07 PM8/11/12
to mongo...@googlegroups.com
Also, look in the logs for the new secondary for percentage signs ("%").  Typically, if you see those, then your system is building indexes.
Reply all
Reply to author
Forward
0 new messages