Currently there are no guardrails that prevent users from spinning up a shard with improper mongod parameters. Even though it is user responsibility to make sure processes are started with the correct flags, we could put in place some guardrails to detect at least some basic misconfigurations and act accordingly (error? crash the node?).

This ticket is aimed at exploring the possible issues/solutions bad combinations of basic mongod startup parameters.

For example, we should disallow users to (re)start one or more mongod processes part of a shard with the --replset option rather than the correct --shardsvr (unless in maintenance mode).