[SERVER-7136] mongorestore fails to find master of replication set Created: 24/Sep/12 Updated: 10/Dec/14 Resolved: 20/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jean-Marie Gaillourdet | Assignee: | Michael Grundy |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 10.04 LTS, mongodb 2.2.0 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Below is shell session which shows the failure. Note that mongorestore lists user@host:~$ mongorestore --host 127.0.0.1:27019,127.0.0.1:27018 -d mydb --drop -c User mongo-dump/mydb/User.bson Mon Sep 24 16:37:31 successfully connected to seed 127.0.0.1:27018 for replica set Mon Sep 24 16:37:33 warning: No primary detected for set |
| Comments |
| Comment by Michael Grundy [ 11/Mar/13 ] | |
|
Hi - Are you still running into this issue? I noticed you were running version 2.2.0 when you initially posted this. We've fixed some critical bugs in 2.2.0 since then and recommend you update to the latest stable release of 2.2, which is 2.2.3, as soon as possible. If you are still seeing this issue with 2.2.3, I'd recommend posting on one of our free support channels. Filing tickets under the SERVER project is not the best way to get visibility for issues you encounter, as we use this project for tracking bugs and feature requests. If you have a support contract with 10gen, then filing commercial support tickets is your best option. If not, the 10gen development and support teams actively monitor posts to stackoverflow (http://stackoverflow.com/questions/tagged/mongodb) and to the mongo google group (https://groups.google.com/forum/?fromgroups#!forum/mongodb-user) Mike | |
| Comment by Jean-Marie Gaillourdet [ 24/Sep/12 ] | |
|
I'll make another run to copy the output and post it here. | |
| Comment by Jean-Marie Gaillourdet [ 24/Sep/12 ] | |
|
Oh, yes. I noticed that now as well. But, when I do that, mongorestore still fails as soon as the master switches. | |
| Comment by Randolph Tan [ 24/Sep/12 ] | |
|
Hi, To specify a replica set as your target, use the replica set connection string, which looks like this: replSet/host1,host2,host3 so in your case, it will look like this:
|