You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Marco Massenzio (JIRA)" <ji...@apache.org> on 2015/08/31 20:06:45 UTC
[jira] [Created] (MESOS-3340) Command-line flags should take
precedence over OS Env variables
Marco Massenzio created MESOS-3340:
--------------------------------------
Summary: Command-line flags should take precedence over OS Env variables
Key: MESOS-3340
URL: https://issues.apache.org/jira/browse/MESOS-3340
Project: Mesos
Issue Type: Improvement
Components: stout
Affects Versions: 0.24.0
Reporter: Marco Massenzio
Currently, it appears that re-defining a flag on the command-line that was already defined via a OS Env var ({{MESOS_*}}) causes the Master to fail with a not very helpful message.
For example, if one has {{MESOS_QUORUM}} defined, this happens:
{noformat}
$ ./mesos-master --zk=zk://192.168.1.4/mesos --quorum=1 --hostname=192.168.1.4 --ip=192.168.1.4
Duplicate flag 'quorum' on command line
{noformat}
which is not very helpful.
Ideally, we would parse the flags with a "well-known" priority (command-line first, environment last) - but at the very least, the error message should be more helpful in explaining what the issue is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)