Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
2.4.8, 2.6.3
-
None
-
Minor Change
-
ALL
Description
I had a server member of replSet asyaRS.
I restarted the mongod with --replSet NotAsya and it happily came up and identified itself as member of asyaRS (since local already had the repl set config there).
It would be safer if we instead complained about replSet argument on command line not matching the stored one.
> rs.conf()._id
|
asyaRS
|
> rs.status().set
|
asyaRS
|
> db.serverCmdLineOpts().parsed.replication
|
{ "replSet" : "NotAsya" }
|
Attachments
Issue Links
- related to
-
SERVER-15689 Poor error message when replica set names don't match during startup
-
- Closed
-