Date: Sat, 11 Aug 2012 14:02:12 -0700 (PDT)
From: Chris Winslett <ch...@mongohq.com>
To: mongodb-dev@googlegroups.com
Message-Id: <ff65505d-3c3c-437f-b7c5-0b9ff6da3d73@googlegroups.com>
In-Reply-To: <64f622f3-f7c4-482f-8cf6-c97bf090b7bd@googlegroups.com>
References: <64f622f3-f7c4-482f-8cf6-c97bf090b7bd@googlegroups.com>
Subject: Re: Master - Slave Replication - Initial Sync taking lot of time
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_835_33173303.1344718932480"

------=_Part_835_33173303.1344718932480
Content-Type: multipart/alternative; 
	boundary="----=_Part_836_3276112.1344718932480"

------=_Part_836_3276112.1344718932480
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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

On Friday, August 10, 2012 7:38:32 AM UTC-5, prasanna venkatesan wrote:
>
> 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
>

------=_Part_836_3276112.1344718932480
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Typically, the longest time during the initial sync is building indexes -- =
particularly if you have larger indexes. &nbsp;We see 30 GB / hour data tra=
nsfers on AWS -- however, building an index can take much longer.<div><div>=
<br></div><div>Chris</div><div>MongoHQ<br><br>On Friday, August 10, 2012 7:=
38:32 AM UTC-5, prasanna venkatesan wrote:<blockquote class=3D"gmail_quote"=
 style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-=
left: 1ex;">Hello Folks<div><br></div><div>&nbsp; Probably this question ha=
s been discussed before but i could not find any of them . This is my issue=
</div><div><br></div><div>&nbsp; We just need a data back up set up and hen=
ce choose to go for master slave set up and not replication . We dont want =
automated failover</div><div><br></div><div>&nbsp; My master data has few h=
undred documents in about 4 collections . I set up a slave and initiated re=
plication . 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 w=
ith new entries every 10 seconds</div><div><br></div><div>&nbsp; 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 .&nbsp;</div><div><br></div>=
<div>&nbsp; Any help would be appreciated</div><div><br></div><div>Thanks</=
div><div>Prasanna</div></blockquote></div></div>
------=_Part_836_3276112.1344718932480--

------=_Part_835_33173303.1344718932480--