[SERVER-20069] 2.4 format config file option 'configsvr = false' not accepted in 3.0 Created: 20/Aug/15 Updated: 06/Dec/22 Resolved: 20/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.0.3, 3.0.4, 3.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Jared Wadsworth | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
The 2.4 format configuration file accepts the option: configsvr = false which equates to the default, that this server is not a config server. This option is also accepted in 2.6. In 3.0, specifying this option causes an error at startup: F CONTROL Failed global initialization: BadValue configsvr option cannot be set to false in config file This breaks backward compatibility with older configuration files. It can be worked around by removing the option. |
| Comments |
| Comment by Eric Milkie [ 20/Nov/15 ] |
|
INI-style config files are deprecated starting in version 3.0; the new YAML format config file is supported. While it was unintentional to break backwards compatibility, we unfortunately do not have resources to spend on fixing this issue for version 3.0, and an easy workaround exists. |