[SERVER-26487] mongod incorrectly allows config servers to be started without journaling if specified in the config file Created: 05/Oct/16 Updated: 06/Dec/22 Resolved: 02/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding 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: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Config servers require journaling to be on to support committed reads. If you try to specify --nojournal with --configsvr on the command line, we correctly error. If, however, you specify storage.journal.enabled:false in a config file along with sharing.clusterRole:configsvr, we allow it. This can cause all majority reads against the config servers to fail, rendering the cluster unusable. |
| Comments |
| Comment by Sheeri Cabral (Inactive) [ 02/Jan/20 ] |
|
This is a first-touch problem but it is not one people seem to be having. |
| Comment by Spencer Brody (Inactive) [ 05/Oct/16 ] |
|
I suspect that had Sam's changes from |