Command line flags are parsed using stout/flags.hpp[0] and the FlagsBase class is derived in mesos::internal::master::Flags (see src/master/flags.hpp[1]).
I am not sure why you are seeing that behavior on CoreOS, but I'd be curious to know what happens if you omit the --quorum when you start master: it should usually fail and complain that it's a required flag (when used in conjunction with --zk). If it works, it will emit in the logs (towards the very beginning) all the values of the flags: what does it say about --quorum? Completely random question: I assume you don't already have in the environment a MESOS_QUORUM variable exported? If the issue persists in a "clean" OS install and a recent build, it's definitely a bug: it'd be great if you could please file a ticket at http://issues.apache.org/jira (feel free to assign to me). Thanks! [0] https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob;f=3rdparty/libprocess/3rdparty/stout/include/stout/flags.hpp [1] https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob;f=src/master/flags.hpp *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com <http://codetrips.com>* On Sun, Aug 30, 2015 at 8:21 PM, F21 <f21.gro...@gmail.com> wrote: > I've gotten the mesos binaries compiled and packaged and deployed them > onto a CoreOS instance. > > > When I run the master, it complains that the quorum flag is duplicated: > > $ ./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 > ... > > However, if I try and run mesos-master on Ubuntu 15.04 64-bit (where the > binaries were built), it seems to work properly: > > $ ./mesos-master --zk=zk://192.168.1.4/mesos --quorum=1 > --hostname=192.168.1.4 --ip=192.168.1.4 > > I0830 18:31:20.983999 2830 main.cpp:181] Build: 2015-08-30 10:11:54 by > I0830 18:31:20.984246 2830 main.cpp:183] Version: 0.23.0 > I0830 18:31:20.984694 2830 main.cpp:204] Using 'HierarchicalDRF' > allocator --work_dir needed for replicated log based registry > > How are the command line flags parsed in mesos? What causes this strange > behavior on CoreOS? > > >
