copy collections to different database? Dev->QA, QA->PROD etc

From: Lee Fisher <fisher.lee@xxxxxxxxx>
To: mongodb-user <mongodb-user@xxxxxxxxxxxxxxxx>
Date: Wed, 11 May 2016 12:46:18 -0700 (PDT)
Why ads?
Is there a preferred method to copy collections to another database?  For 
example when we move from DEV to QA or QA to PRODUCTION.
PRODUCTION would be 3 member replicaset, others are single instances.

Currently we use mongodump mongorestore and exclude the few collections we 
do not want.

Generally it works OK, but we have noticed sometimes during/after copying 
to PRODUCTION the replicaset members could hit 400% CPU and may cause 
degraded performance.

Is this the preferred method or is there another way?

Thanks,
Lee

-- 
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/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+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to mongodb-user@xxxxxxxxxxxxxxxx.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/6badb5ff-174d-43d3-802f-b920048ebbff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Why ads?