Adding a replica in MongoDB throws an error

Question

I'm trying to add a node to a replica set using rs.add("developer-ViratualBox:30103") and I'm getting the following error message:

{
"ok" : 0,
"errmsg" : "Quorum check failed because not enough voting nodes responded; required 2 but only the following 1 voting nodes responded: developer-VirtualBox:30101; the following nodes did not respond affirmatively: developer-ViratualBox:30103 failed with Failed attempt to connect to developer-ViratualBox:30103; couldn't initialize connection to host developer-ViratualBox, address is invalid",
"code" : 74
}

The node is already running and I'm connected to it using mongo shell. What could possibly be the problem?

yes. please see my answer – Ahmad Hosny Feb 29 '16 at 11:44 — Ahmad Hosny, Feb 29 '16 at 11:44

score 4 · Answer 1 · answered Oct 27 '15 at 07:27

The actual error is couldn't initialize connection to host developer-ViratualBox, address is invalid, Simply the primary node is not able to connect with secondery nodes. check connections, firewall, and check connection with mongo shell whether you can access that port or not.

score 1 · Accepted Answer · answered Feb 29 '16 at 11:46

1

The missing point is that the instance that I was trying to add did not have mongod instance started at the port defined. The given connection parameters hence were incorrect, and that caused the communication problem.

answered Feb 29 '16 at 11:46

Ahmad Hosny

597
1
6
23

this is really helpful. btw I am setting mongo cluster on localhost. do you have a doc file for this? can you share it. – roottraveller Nov 15 '19 at 13:24
did you host one on localhost and one else where? I can't seem to get it to work. – DUDANF Dec 04 '19 at 15:36
@mirana no, all the instances were on localhost – Ahmad Hosny Dec 05 '19 at 16:11

score 1 · Answer 3 · answered Apr 11 '16 at 18:15

1

While starting secondary mongod process use --replSet option the try to run rs.add("localhost:27002") from primary mongod shell.

answered Apr 11 '16 at 18:15

Raju Lalli

11
1

Govinda Shaw · Answer 4 · 2018-05-31T10:56:55.980

While creating rsconf file please enter <localhost:port> instead of <hostname:port>. And then reconfig(rsconf).

example :

rs0:PRIMARY>     
rsconf = {
             _id: "rs0",
             members: [
                 {
                     _id: 0,
                     host: "**localhost**:port for primary rs"
                 }]
         }

rs0:PRIMARY> rs.initiate(rsconf)
    {
        "info" : "try querying local.system.replset to see current configuration",
        "ok" : 0,
        "errmsg" : "already initialized",
        "code" : 23
    }

If you are getting above error then use the below command:

rs0:PRIMARY> rs.reconfig(rsconf)

Adding secondary node : rs.add("localhost:port for secondary rs")

Hope it will work.

Unfortunately no. The nodes were not on the same machine. – Ahmad Hosny Jun 18 '18 at 15:02 — Ahmad Hosny, Jun 18 '18 at 15:02

score 0 · Answer 5 · answered May 27 '15 at 11:03

0

You can only add members while connected to the primary. To know which member is the primary, log into any member of the replica set and issue the db.isMaster() command.

Then, use rs.add() to add the new member to the replica set. For example, to add a member at host mongodb3.example.net, issue the following command:

rs.add("developer-ViratualBox:30103")

answered May 27 '15 at 11:03

vmr

1,895
13
24

2

I get this error while connected to primary, trying to add secondary – Vao Tsun Oct 13 '15 at 09:18

score 0 · Answer 6 · answered Apr 26 '17 at 10:23

Another possible issue is that the machine that you are trying to add to the replica set is not configured to run with replication. Adding this entry to the mongod.conf on the machine that you're trying to add and restarting the service worked for me:

replication:
  replSetName: evoReplicaSet

score -3 · Answer 7 · answered Aug 18 '20 at 08:07

-3

you should use docker network to solve this problem.

answered Aug 18 '20 at 08:07

Đỗ Hoàng

1

1

Your answer is too general. Please add some explanation and samples. – mate00 Aug 18 '20 at 08:49
This instance was not a part of a docker network, nor on a docker container – Ahmad Hosny Aug 22 '20 at 10:59

Adding a replica in MongoDB throws an error

7 Answers7