Re: Issues in moving to 2.2 with replication set name in a configuration file

[Jenna deBoisblanc]

Please feel free to file, track, and up vote a ticket in JIRA to
request a field-parsing change.
https://jira.mongodb.org/

On Oct 25, 10:53 am, Sean Kidder <skid...@geopayinc.com> wrote:
> We had an odd issue with a recent upgrade from 2.0.7 to 2.2.0.  We are
> using replication, and there is a file containing our startup configuration
> that is referenced when mongo starts.  In the file, the replication set was
> defined as:
>
> replSet = "real_replica_set_name"
>
> When we upgraded, we started receiving errors in the log as follows:
>
> replSet exception loading our local replset configuration object : 13132
> nonmatching repl set name in _id field: real_replica_set_name vs.
> "real_replica_set_name"
>
> We solved the problem by taking the double quotes out of the replSet
> definitikion for all the configuration files, so the line in the config
> file now looks like this:
>
> replSet = real_replica_set_name
>
> But I was disappointed 2.2.0 changed how this field is parsed and think it
> should, like any configuration files in Linux, ought to be able to deal
> with enclosing double quotes.