MongoDb Primary tries to connect a member already deleted

I removed one member from a set of 2-member replicas. But the primary still tries to connect to that node.

rs.conf result:

/ * one * /
{
"_id": "ReplicaSet",
"version": 84,
"protocolVersion": NumberLong (1),
"writeConcernMajorityJournalDefault": true,
"members": [ 
        {
            "_id" : 8,
            "host" : "--------:20001",
            "arbiterOnly" : true,
            "buildIndexes" : true,
            "hidden" : true,
            "priority" : 0.0,
            "tags" : {},
            "slaveDelay" : NumberLong(0),
            "votes" : 1
        }, 
        {
            "_id" : 11,
            "host" : "--------:20001",
            "arbiterOnly" : false,
            "buildIndexes" : true,
            "hidden" : false,
            "priority" : 2.0,
            "tags" : {},
            "slaveDelay" : NumberLong(0),
            "votes" : 1
        }
    ],
"configuration": {
"chaining allowed": true,
"heartbeatIntervalMillis": 2000,
"heartbeatTimeoutSecs": 10,
"electionTimeoutMillis": 10000,
"catchUpTimeoutMillis": 2000,
"catchUpTakeoverDelayMillis": 30000,
"getLastErrorModes": {},
"getLastErrorDefaults": {
"w": 1,
"wtimeout": 0
}
"replicaSetId": ObjectId ("5744440acea85c16a08e23ce")
}
}

I even started another MongoDb node in that destination that the registry is like the following.

2018-11-22T01: 40: 03.428 + 0330 I REPL_HB  [replexec-81] Heartbeat error (requestId: 85325) to --------: 20002, response status: InvalidReplicaSetConfig: our replica set configuration is not valid or does not include us
2018-11-22T01: 40: 03.429 + 0330 I REPL_HB  [replexec-83] Heartbeat error (requestId: 85326) to -------: 20002, response status: InvalidReplicaSetConfig: our replica set configuration is not valid or does not include us

Any ideas? Why is the primary still trying to connect to the deleted node?