We are in the process of moving our MongoDb replication sets to new hardware but is encountering a problem when adding our new replication set to the cluster.
2017-03-28T20:07:18.434+0200 W NETWORK [ReplicaSetMonitorWatcher] No primary detected for set mongoset004
2017-03-28T20:07:28.442+0200 I NETWORK [ReplicaSetMonitorWatcher] node mongosrv014:27018 believes it is primary, but its election id of 7fffffff0000000000000005 and config version of 3 is older than the most recent election id 7fffffff000000000000002c and config version of 71238
2017-03-28T20:07:28.443+0200 I NETWORK [ReplicaSetMonitorWatcher] node 192.168.1.93:27018 believes it is primary, but its election id of 7fffffff0000000000000005 and config version of 3 is older than the most recent election id 7fffffff000000000000002c and config version of 71238
We ended up in this state after removing the old replication set by following the guide to remove shards from a cluster. Then we replaced the servers with our new ones (keeping their names and ip addresses) and configured the "new" MongoDb set on these servers and tried to add them to the cluster once more
sh.addShard('mongoset004/mongosrv014:27018,mongosrv015:27018,mongosrv016:27018')
We've probably missed something crucial when removing the original cluster but can't find any documentation that points us in the right direction.