[GODRIVER-744] Vanilla mongodb instance with --replicaSet option set, is not valid for any operations (Kind == "Unknown") Created: 03/Jan/19 Updated: 11/Sep/19 Resolved: 22/Jan/19 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | Options & Configuration |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Audrius Karabanovas | Assignee: | Kristofer Brandow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Issue discovered trying to writing go program to initiate replicaSet trough driver, if server was run with --replicaSet flag (before initiating it in console), driver fails to run any commands/client.Ping() with server selection timeout error. Connecting to server trough mongo console and doing rs.initiate() + rs.reconfigure() with current connection string e.x. localhost:27017 as members[0].host fixes issue. Looks like topology just doesn't work with not initialised replicaSet |
| Comments |
| Comment by Kristofer Brandow (Inactive) [ 04/Jan/19 ] |
|
Hi shivas, If you want to use the driver to configure a replica set you need to use connect=direct mode. That will ensure that you can properly select the server to configure. Please report back if this works. Thanks, Kris |