[SERVER-15689] Poor error message when replica set names don't match during startup Created: 16/Oct/14  Updated: 16/Dec/14  Resolved: 06/Nov/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.7.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-14683 starting server with wrong replSet do... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

When the stored replica set config doesn't match the configured name, this message appears:

set names do not match, ours: <cmdline-name>; remote node's: <stored-name>

mongod --replSet n1
{_id:"n2", version:2, members:...}



 Comments   
Comment by Scott Hernandez (Inactive) [ 06/Nov/14 ]

Some other change caused this to disappear...

Now looks like this:

2014-11-06T12:48:32.990-0500 I REPLSETS [rsSync] replSet warning did not receive a valid config yet, sleeping 5 seconds 
2014-11-06T12:48:32.991-0500 I NETWORK  [initandlisten] waiting for connections on port 27017
2014-11-06T12:48:33.487-0500 W REPLSETS [ReplicationExecutor] Local replica set configuration document reports set name of test7, but command line reports test12; waitng for reconfig or remote heartbeat
2014-11-06T12:48:33.487-0500 I REPLSETS [ReplicationExecutor] transition to REMOVED

Comment by Scott Hernandez (Inactive) [ 17/Oct/14 ]

It comes up in the logs at startup, if you use the "wrong" replica set name on an already configured node.

I would like the message to correctly reflect which values conflict – the command line and local/saved config replica set names.

Comment by Eric Milkie [ 17/Oct/14 ]

From your description, I'm not clear when the message appears. Does it appear when you try to, for example, initiate with a config on that same node? If so, then the message should be changed to not say "remote node" – is that what you meant for this ticket?

Generated at Thu Feb 08 03:38:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.