[SERVER-24551] Version 3.2 incorrect 'nojournal is not allowed when configsvr is specified' error when specifying nojournal=false Created: 14/Jun/16 Updated: 06/Dec/22 Resolved: 19/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Blue Medora EngOps | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||
| Steps To Reproduce: | Use this config file and try to start MongoDB 3.2:
If I remove the nojournal = false line, everything works perfectly. However, this is bad functionality as it means my config files aren't as portable as they should be. Passing an option as false shouldn't be picked up by the error checking as if I was passing it as true. |
||||||||||||||||||
| Sprint: | Sharding 16 (06/24/16), Sharding 17 (07/15/16) | ||||||||||||||||||
| Participants: | |||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||
| Description |
|
After installing MongoDB 3.2 it will not start, so checking status I get:
Clearly showing that even passing nojournal=false is read by the error as passing nojournal=true. This is bad form. See next section for steps to reproduce. |
| Comments |
| Comment by Sheeri Cabral (Inactive) [ 19/Dec/19 ] |
|
There's merit in having an error with conflicting parameters; should the server believe nojournal=false or configsvr=true. |
| Comment by Githook User [ 01/Sep/16 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: Revert " This reverts commit 67680aae26d7734e899976d020018b9cad474671. |
| Comment by Githook User [ 01/Sep/16 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: Revert "Revert " This reverts commit 82a188cc0a0b33badcc64f294908b1f629b0fb05. |
| Comment by Githook User [ 10/Aug/16 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: Revert " This reverts commit 67680aae26d7734e899976d020018b9cad474671. |
| Comment by Spencer Brody (Inactive) [ 01/Aug/16 ] |
|
If this ever gets backported https://github.com/mongodb/mongo/commit/750754153357481e40c498f1def3371af79f2309 should be backported as well |
| Comment by Githook User [ 07/Jul/16 ] |
|
Author: {u'name': u'Sam Dunietz', u'email': u'sam.dunietz@10gen.com'}Message: |
| Comment by Andy Schwerin [ 15/Jun/16 ] |
|
The problem here is that the MongoDB options parser allows us easily to set constraints on what command line arguments and config file directives are incompatible with each other, but it is harder to say which flag values are incompatible with each other. As a result, the author of some prior patch forbade mentioning --nojournal and --configsvr in the same configuration, even if the requested setting of the values is compatible. |