Master and Agent Options
These options can be supplied to both masters and agents.
Flag | Explanation |
---|---|
--advertise_ip=VALUE | IP address advertised to reach this Mesos master/agent. The master/agent does not bind to this IP address. However, this IP address may be used to access this master/agent. |
--advertise_port=VALUE |
Port advertised to reach this Mesos master/agent (along with
advertise_ip ). The master/agent does not bind using this port.
However, this port (along with advertise_ip ) may be used to
access Mesos master/agent.
|
--[no-]authenticate_http_readonly |
If true , only authenticated requests for read-only HTTP endpoints
supporting authentication are allowed. If false , unauthenticated
requests to such HTTP endpoints are also allowed.
|
--[no-]authenticate_http_readwrite |
If true , only authenticated requests for read-write HTTP endpoints
supporting authentication are allowed. If false , unauthenticated
requests to such HTTP endpoints are also allowed.
|
--firewall_rules=VALUE |
The value could be a JSON-formatted string of rules or a
file path containing the JSON-formatted rules used in the endpoints
firewall. Path must be of the form file:///path/to/file
or /path/to/file .
See the Firewall message in flags.proto for the expected format.
Example:
|
--domain=VALUE |
Domain that the master or agent belongs to. Mesos currently only supports
fault domains, which identify groups of hosts with similar failure
characteristics. A fault domain consists of a region and a zone. All masters
in the same Mesos cluster must be in the same region (they can be in
different zones). Agents configured to use a different region than the
master's region will not appear in resource offers to frameworks that have
not enabled the REGION_AWARE capability. This value can be
specified as either a JSON-formatted string or a file path containing JSON.
See the documentation for further details. Example:
|
--[no-]help | Show the help message and exit. (default: false) |
--hooks=VALUE | A comma-separated list of hook modules to be installed inside master/agent. |
--hostname=VALUE |
The hostname the agent node should report, or that the master
should advertise in ZooKeeper.
If left unset, the hostname is resolved from the IP address
that the master/agent binds to; unless the user explicitly prevents
that, using --no-hostname_lookup , in which case the IP itself
is used.
|
--[no-]hostname_lookup |
Whether we should execute a lookup to find out the server's hostname,
if not explicitly set (via, e.g., --hostname ).
True by default; if set to false it will cause Mesos
to use the IP address, unless the hostname is explicitly set. (default: true)
|
--http_authenticators=VALUE |
HTTP authenticator implementation to use when handling requests to
authenticated endpoints. Use the default basic , or load an
alternate HTTP authenticator module using --modules .
(default: basic, or basic and JWT if executor authentication is enabled)
|
--ip=VALUE |
IP address to listen on. This cannot be used in conjunction
with --ip_discovery_command .
|
--ip_discovery_command=VALUE |
Optional IP discovery binary: if set, it is expected to emit
the IP address which the master/agent will try to bind to.
Cannot be used in conjunction with --ip .
|
--modules=VALUE |
List of modules to be loaded and be available to the internal
subsystems.
Use --modules=filepath to specify the list of modules via a
file containing a JSON-formatted string. filepath can be
of the form file:///path/to/file or /path/to/file .
Use --modules="{...}" to specify the list of modules inline.
Example:
Cannot be used in conjunction with --modules_dir.
|
--modules_dir=VALUE |
Directory path of the module manifest files. The manifest files are processed in
alphabetical order. (See --modules for more information on module
manifest files). Cannot be used in conjunction with --modules .
|
--port=VALUE | Port to listen on. (master default: 5050; agent default: 5051) |
--[no-]version | Show version and exit. (default: false) |
--zk_session_timeout=VALUE | ZooKeeper session timeout. (default: 10secs) |
Logging Options
These logging options can also be supplied to both masters and agents. For more about logging, see the logging documentation.
Flag | Explanation |
---|---|
--[no-]quiet | Disable logging to stderr. (default: false) |
--log_dir=VALUE | Location to put log files. By default, nothing is written to disk. Does not affect logging to stderr. If specified, the log file will appear in the Mesos WebUI. NOTE: 3rd party log messages (e.g. ZooKeeper) are only written to stderr! |
--logbufsecs=VALUE | Maximum number of seconds that logs may be buffered for. By default, logs are flushed immediately. (default: 0) |
--logging_level=VALUE |
Log message at or above this level.
Possible values: INFO , WARNING , ERROR .
If --quiet is specified, this will only affect the logs
written to --log_dir , if specified. (default: INFO)
|
--[no-]initialize_driver_logging | Whether the master/agent should initialize Google logging for the scheduler and executor drivers, in the same way as described here. The scheduler/executor drivers have separate logs and do not get written to the master/agent logs. This option has no effect when using the HTTP scheduler/executor APIs. (default: true) |
--external_log_file=VALUE |
Location of the externally managed log file. Mesos does not write to
this file directly and merely exposes it in the WebUI and HTTP API.
This is only useful when logging to stderr in combination with an
external logging mechanism, like syslog or journald.
This option is meaningless when specified along with --quiet .
This option takes precedence over --log_dir in the WebUI.
However, logs will still be written to the --log_dir if
that option is specified.
|