[SERVER-8809] Print additional warnings/ notices for non-recommended configurations Created: 01/Mar/13  Updated: 04/Jun/13  Resolved: 04/Jun/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Nicholas Tang Assignee: Unassigned
Resolution: Incomplete Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

The startup warnings printed:
https://github.com/mongodb/mongo/blob/master/src/mongo/util/version.cpp#L176

...don't match the recommendations in the documentations for ulimits:
http://docs.mongodb.org/manual/administration/ulimit/

...or the recommendations in the Production Notes:
http://docs.mongodb.org/manual/administration/production-notes/

My suggestion: add warnings/ notices in the logs (and warnings on the command line stdout or stderr) anytime a setting doesn't match the documented recommendations.

Ex: "[notice] Your open files system ulimit (value) is currently below our recommended settings. You can read more about that here: http://docs.mongodb.org/manual/administration/ulimit/"

Another example: "[warning] Your replicaset has an even number of nodes, which may prevent it from electing a new primary in case of a server failure. You can read more here: http://docs.mongodb.org/manual/core/replication/#architectures"



 Comments   
Comment by Ian Whalen (Inactive) [ 04/Jun/13 ]

nicholas.tang@10gen.com I'm closing this because it's a bit open-ended as written and will be difficult to ever consider fully resolved. Could you please open up a ticket for each individual mismatch between docs and warning that you believe should be fixed? That way we can discuss, prioritize, and work on each one individually.

Comment by Nicholas Tang [ 01/Mar/13 ]

I should've been more explicit, but that's why I said "anytime a setting doesn't match the documented recommendations". I agree, the replicaset note would happen at runtime when an appropriate command was kicked off.

Generated at Thu Feb 08 03:18:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.