Replication is very slow to a newly added Replica Node to an existing ReplicaSet.

[Durga Deep]

Hi Folks

   We have a 5 node ReplicaSet which currently holds 45 GB of data, and we added another 2 members to the replica Set and for some reason the replication is taking way too long, it took nearly 10 hours for the data to be available in this newly added replicaSet.

Questions --

   How to find out where the performance bottle-neck is ?

   Any tips of how this can be remedied ?, better disk space etc. ?.

Thanks

_DD

[Asya Kamsky]

Presumably the new replica set members have the same type of disk that
current ones had?

I would look at the network throughput and at how long it took to
build indexes - if pulling all the data over took a long time then
network may be limiting replication speed, if building indexes is
where the issue was then maybe CPU speed was the limitation.

In any case, the fastest way to bring up a new replica node is not to
let it sync itself but to start it out with a copy of the filesystem
snapshot from one of the existing nodes in the replica set.

Asya

> --
> You received this message because you are subscribed to the Google Groups
> "mongodb-user"
> group.
>
> For other MongoDB technical support options, see:
> http://www.mongodb.org/about/support/.
> ---
> You received this message because you are subscribed to the Google Groups
> "mongodb-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mongodb-user...@googlegroups.com.
> To post to this group, send email to mongod...@googlegroups.com.
> Visit this group at http://groups.google.com/group/mongodb-user.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mongodb-user/516d438b-7ff2-4765-9b4f-f572ad04aa94%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.