[SERVER-14384] Error while replicating sharded cluster environment Created: 28/Jun/14 Updated: 10/Dec/14 Resolved: 16/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Pratik Gadiya [X] | Assignee: | Thomas Rueckstiess |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi, I wanted to replicate the production sharding cluster environment on staging systems. Error on configsvr :
Error for Mongos :
Thanks |
| Comments |
| Comment by Thomas Rueckstiess [ 16/Jul/14 ] |
|
Hi Pratik, You can find instructions how to migrate a cluster in the documentation under Migrate a Sharded Cluster. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. Regards, |
| Comment by Pratik Gadiya [X] [ 03/Jul/14 ] |
|
Thanks for the help. I tried to resolve the config server by the steps mentioned above, but still facing the same issue. Can you let me know all the steps which I need to perform in order to migrate data from one sharded cluster to another sharded cluster ? Thanks |
| Comment by Thomas Rueckstiess [ 30/Jun/14 ] |
|
Hi Pratik, This looks like a corruption in the data, because the document claims to be 859MB of size, which of course is impossible. How exactly did you copy the data over? If you did a simple file copy, did you lock the database for writes (fsyncLock) before copying the data? If not, that could explain the corruption as you were copying the files while they were written to. In order to get a consistent copy, you need to either use a filesystem snapshot, a mongodump with the --oplog option, or you need to stop writes before the copy. You can also bring down one secondary before the copy, then start it again. For the config servers, you can bring down the third config server, copy the data and start it again. Also make sure that the balancer is disabled and not running before you copy the data. That way your prod system stays operational and you will get a consistent copy. Our documentation page on Backup of Sharded Clusters gives you a detailed explanation of the various options. Can you let me know if one of these suggestions fixes your issue? Thanks |