Repository: mesos-site Updated Branches: refs/heads/asf-site 88650024b -> a5fb0e1cc
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/configuration/master-and-agent/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/configuration/master-and-agent/index.html b/content/documentation/latest/configuration/master-and-agent/index.html new file mode 100644 index 0000000..3362db0 --- /dev/null +++ b/content/documentation/latest/configuration/master-and-agent/index.html @@ -0,0 +1,535 @@ +<!DOCTYPE html> +<html> + <head> + <meta charset="utf-8"> + <title>Apache Mesos - Master and Agent Options</title> + <meta name="viewport" content="width=device-width, initial-scale=1.0"> + + <meta property="og:locale" content="en_US"/> + <meta property="og:type" content="website"/> + <meta property="og:title" content="Apache Mesos"/> + <meta property="og:site_name" content="Apache Mesos"/> + <meta property="og:url" content="http://mesos.apache.org/"/> + <meta property="og:image" content="http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/> + <meta property="og:description" + content="Apache Mesos abstracts resources away from machines, + enabling fault-tolerant and elastic distributed systems + to easily be built and run effectively."/> + + <meta name="twitter:card" content="summary"/> + <meta name="twitter:site" content="@ApacheMesos"/> + <meta name="twitter:title" content="Apache Mesos"/> + <meta name="twitter:image" content="http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/> + <meta name="twitter:description" + content="Apache Mesos abstracts resources away from machines, + enabling fault-tolerant and elastic distributed systems + to easily be built and run effectively."/> + + <link href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css" rel="stylesheet"> + <link rel="alternate" type="application/atom+xml" title="Apache Mesos Blog" href="/blog/feed.xml"> + <link href="../../../../assets/css/main.css" media="screen" rel="stylesheet" type="text/css" /> + + + + <!-- Google Analytics Magic --> + <script type="text/javascript"> + var _gaq = _gaq || []; + _gaq.push(['_setAccount', 'UA-20226872-1']); + _gaq.push(['_setDomainName', 'apache.org']); + _gaq.push(['_trackPageview']); + + (function() { + var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; + ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; + var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); + })(); + </script> + + </head> + <body> + <!-- magical breadcrumbs --> + <div class="topnav"> + <div class="container"> + <ul class="breadcrumb"> + <li> + <div class="dropdown"> + <a data-toggle="dropdown" href="#">Apache Software Foundation <span class="caret"></span></a> + <ul class="dropdown-menu" role="menu" aria-labelledby="dLabel"> + <li><a href="http://www.apache.org";>Apache Homepage</a></li> + <li><a href="http://www.apache.org/licenses/";>License</a></li> + <li><a href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li> + <li><a href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li> + <li><a href="http://www.apache.org/security/";>Security</a></li> + </ul> + </div> + </li> + + <li><a href="http://mesos.apache.org";>Apache Mesos</a></li> + + + <li><a href="/documentation +/">Documentation +</a></li> + + + </ul><!-- /.breadcrumb --> + </div><!-- /.container --> + </div><!-- /.topnav --> + + <!-- navbar excitement --> +<div class="navbar navbar-default navbar-static-top" role="navigation"> + <div class="container"> + <div class="navbar-header"> + <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#mesos-menu" aria-expanded="false"> + <span class="sr-only">Toggle navigation</span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + <a class="navbar-brand" href="/"><img src="/assets/img/mesos_logo.png" alt="Apache Mesos logo"/></a> + </div><!-- /.navbar-header --> + + <div class="navbar-collapse collapse" id="mesos-menu"> + <ul class="nav navbar-nav navbar-right"> + <li><a href="/gettingstarted/">Getting Started</a></li> + <li><a href="/blog/">Blog</a></li> + <li><a href="/documentation/latest/">Documentation</a></li> + <li><a href="/downloads/">Downloads</a></li> + <li><a href="/community/">Community</a></li> + </ul> + </div><!-- /#mesos-menu --> + </div><!-- /.container --> +</div><!-- /.navbar --> + +<div class="content"> + <div class="container"> + <div class="row-fluid"> + <div class="col-md-4"> + <h4>If you're new to Mesos</h4> + <p>See the <a href="/gettingstarted/">getting started</a> page for more + information about downloading, building, and deploying Mesos.</p> + + <h4>If you'd like to get involved or you're looking for support</h4> + <p>See our <a href="/community/">community</a> page for more details.</p> + </div> + <div class="col-md-8"> + <h1>Master and Agent Options</h1> + +<p><em>These options can be supplied to both masters and agents.</em></p> + +<table class="table table-striped"> + <thead> + <tr> + <th width="30%"> + Flag + </th> + <th> + Explanation + </th> + </tr> + </thead> +<tr> + <td> + --advertise_ip=VALUE + </td> + <td> +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. + </td> +</tr> +<tr> + <td> + --advertise_port=VALUE + </td> + <td> +Port advertised to reach this Mesos master/agent (along with +<code>advertise_ip</code>). The master/agent does not bind using this port. +However, this port (along with <code>advertise_ip</code>) may be used to +access Mesos master/agent. + </td> +</tr> +<tr> + <td> + --[no-]authenticate_http_readonly + </td> + <td> +If <code>true</code>, only authenticated requests for read-only HTTP endpoints +supporting authentication are allowed. If <code>false</code>, unauthenticated +requests to such HTTP endpoints are also allowed. + </td> +</tr> +<tr> + <td> + --[no-]authenticate_http_readwrite + </td> + <td> +If <code>true</code>, only authenticated requests for read-write HTTP endpoints +supporting authentication are allowed. If <code>false</code>, unauthenticated +requests to such HTTP endpoints are also allowed. + </td> +</tr> +<tr> + <td> + --firewall_rules=VALUE + </td> + <td> +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 <code>file:///path/to/file</code> +or <code>/path/to/file</code>. +<p/> +See the <code>Firewall</code> message in <code>flags.proto</code> for the expected format. +<p/> +Example: +<pre><code>{ + "disabled_endpoints" : { + "paths" : [ + "/files/browse", + "/metrics/snapshot" + ] + } +}</code></pre> + </td> +</tr> +<tr> + <td> + --domain=VALUE + </td> + <td> +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 <code>REGION_AWARE</code> capability. This value can be +specified as either a JSON-formatted string or a file path containing JSON. +<p/> +Example: +<pre><code>{ + "fault_domain": + { + "region": + { + "name": "aws-us-east-1" + }, + "zone": + { + "name": "aws-us-east-1a" + } + } +}</code></pre> + </td> +</tr> +<tr> + <td> + --[no-]help + </td> + <td> +Show the help message and exit. (default: false) + </td> +</tr> +<tr> + <td> + --hooks=VALUE + </td> + <td> +A comma-separated list of hook modules to be installed inside master/agent. + </td> +</tr> +<tr> + <td> + --hostname=VALUE + </td> + <td> +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 <code>--no-hostname_lookup</code>, in which case the IP itself +is used. + </td> +</tr> +<tr> + <td> + --[no-]hostname_lookup + </td> + <td> +Whether we should execute a lookup to find out the server's hostname, +if not explicitly set (via, e.g., <code>--hostname</code>). +True by default; if set to <code>false</code> it will cause Mesos +to use the IP address, unless the hostname is explicitly set. (default: true) + </td> +</tr> +<tr> + <td> + --http_authenticators=VALUE + </td> + <td> +HTTP authenticator implementation to use when handling requests to +authenticated endpoints. Use the default <code>basic</code>, or load an +alternate HTTP authenticator module using <code>--modules</code>. +(default: basic, or basic and JWT if executor authentication is enabled) + </td> +</tr> +<tr> + <td> + --ip=VALUE + </td> + <td> +IP address to listen on. This cannot be used in conjunction +with <code>--ip_discovery_command</code>. + </td> +</tr> +<tr> + <td> + --ip_discovery_command=VALUE + </td> + <td> +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 <code>--ip</code>. + </td> +</tr> +<tr> + <td> + --ip6=VALUE + </td> + <td> +IPv6 address to listen on. This cannot be used in conjunction +with <code>--ip6_discovery_command</code>. +<p/> +NOTE: Currently Mesos doesn't listen on IPv6 sockets and hence +this IPv6 address is only used to advertise IPv6 addresses for +containers running on the host network. + </td> +</tr> +<tr> + <td> + --ip6_discovery_command=VALUE + </td> + <td> +Optional IPv6 discovery binary: if set, it is expected to emit +the IPv6 address on which Mesos will try to bind when IPv6 socket +support is enabled in Mesos. +<p/> +NOTE: Currently Mesos doesn't listen on IPv6 sockets and hence +this IPv6 address is only used to advertise IPv6 addresses for +containers running on the host network. + </td> +</tr> +<tr> + <td> + --modules=VALUE + </td> + <td> +List of modules to be loaded and be available to the internal +subsystems. +<p/> +Use <code>--modules=filepath</code> to specify the list of modules via a +file containing a JSON-formatted string. <code>filepath</code> can be +of the form <code>file:///path/to/file</code> or <code>/path/to/file</code>. +<p/> +Use <code>--modules="{...}"</code> to specify the list of modules inline. +<p/> +Example: +<pre><code>{ + "libraries": [ + { + "file": "/path/to/libfoo.so", + "modules": [ + { + "name": "org_apache_mesos_bar", + "parameters": [ + { + "key": "X", + "value": "Y" + } + ] + }, + { + "name": "org_apache_mesos_baz" + } + ] + }, + { + "name": "qux", + "modules": [ + { + "name": "org_apache_mesos_norf" + } + ] + } + ] +}</code></pre> +<p/> Cannot be used in conjunction with --modules_dir. + </td> +</tr> +<tr> + <td> + --modules_dir=VALUE + </td> + <td> +Directory path of the module manifest files. The manifest files are processed in +alphabetical order. (See <code>--modules</code> for more information on module +manifest files). Cannot be used in conjunction with <code>--modules</code>. + </td> +</tr> +<tr> + <td> + --port=VALUE + </td> + <td> +Port to listen on. (master default: 5050; agent default: 5051) + </td> +</tr> +<tr> + <td> + --[no-]version + </td> + <td> +Show version and exit. (default: false) + </td> +</tr> +<tr> + <td> + --zk_session_timeout=VALUE + </td> + <td> +ZooKeeper session timeout. (default: 10secs) + </td> +</tr> +</table> + + +<h2>Logging Options</h2> + +<p><em>These logging options can also be supplied to both masters and agents.</em> +For more about logging, see the <a href="/documentation/latest/configuration/../logging/">logging documentation</a>.</p> + +<table class="table table-striped"> + <thead> + <tr> + <th width="30%"> + Flag + </th> + <th> + Explanation + </th> + </tr> + </thead> +<tr> + <td> + --[no-]quiet + </td> + <td> +Disable logging to stderr. (default: false) + </td> +</tr> +<tr> + <td> + --log_dir=VALUE + </td> + <td> +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. +<b>NOTE</b>: 3rd party log messages (e.g. ZooKeeper) are +only written to stderr! + </td> +</tr> +<tr> + <td> + --logbufsecs=VALUE + </td> + <td> +Maximum number of seconds that logs may be buffered for. +By default, logs are flushed immediately. (default: 0) + </td> +</tr> +<tr> + <td> + --logging_level=VALUE + </td> + <td> +Log message at or above this level. +Possible values: <code>INFO</code>, <code>WARNING</code>, <code>ERROR</code>. +If <code>--quiet</code> is specified, this will only affect the logs +written to <code>--log_dir</code>, if specified. (default: INFO) + </td> +</tr> +<tr> + <td> + --[no-]initialize_driver_logging + </td> + <td> +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. +<p/> +This option has no effect when using the HTTP scheduler/executor APIs. +(default: true) + </td> +</tr> +<tr> + <td> + --external_log_file=VALUE + </td> + <td> +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. +<p/> +This option is meaningless when specified along with <code>--quiet</code>. +<p/> +This option takes precedence over <code>--log_dir</code> in the WebUI. +However, logs will still be written to the <code>--log_dir</code> if +that option is specified. + </td> +</tr> +</table> + + + </div> +</div> + + </div><!-- /.container --> +</div><!-- /.content --> + +<hr> + + + + <!-- footer --> + <div class="footer"> + <div class="container"> + <div class="col-md-4 social-blk"> + <span class="social"> + <a href="https://twitter.com/ApacheMesos"; + class="twitter-follow-button" + data-show-count="false" data-size="large">Follow @ApacheMesos</a> + <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script> + <a href="https://twitter.com/intent/tweet?button_hashtag=mesos"; + class="twitter-hashtag-button" + data-size="large" + data-related="ApacheMesos">Tweet #mesos</a> + <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script> + </span> + </div> + + <div class="col-md-8 trademark"> + <p>© 2012-2017 <a href="http://apache.org";>The Apache Software Foundation</a>. + Apache Mesos, the Apache feather logo, and the Apache Mesos project logo are trademarks of The Apache Software Foundation. + <p> + </div> + </div><!-- /.container --> + </div><!-- /.footer --> + + <!-- JS --> + <script src="//code.jquery.com/jquery-1.11.0.min.js" type="text/javascript"></script> + <script src="//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js" type="text/javascript"></script> + </body> +</html> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/configuration/master/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/configuration/master/index.html b/content/documentation/latest/configuration/master/index.html new file mode 100644 index 0000000..1f66ab6 --- /dev/null +++ b/content/documentation/latest/configuration/master/index.html @@ -0,0 +1,731 @@ +<!DOCTYPE html> +<html> + <head> + <meta charset="utf-8"> + <title>Apache Mesos - Master Options</title> + <meta name="viewport" content="width=device-width, initial-scale=1.0"> + + <meta property="og:locale" content="en_US"/> + <meta property="og:type" content="website"/> + <meta property="og:title" content="Apache Mesos"/> + <meta property="og:site_name" content="Apache Mesos"/> + <meta property="og:url" content="http://mesos.apache.org/"/> + <meta property="og:image" content="http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/> + <meta property="og:description" + content="Apache Mesos abstracts resources away from machines, + enabling fault-tolerant and elastic distributed systems + to easily be built and run effectively."/> + + <meta name="twitter:card" content="summary"/> + <meta name="twitter:site" content="@ApacheMesos"/> + <meta name="twitter:title" content="Apache Mesos"/> + <meta name="twitter:image" content="http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/> + <meta name="twitter:description" + content="Apache Mesos abstracts resources away from machines, + enabling fault-tolerant and elastic distributed systems + to easily be built and run effectively."/> + + <link href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css" rel="stylesheet"> + <link rel="alternate" type="application/atom+xml" title="Apache Mesos Blog" href="/blog/feed.xml"> + <link href="../../../../assets/css/main.css" media="screen" rel="stylesheet" type="text/css" /> + + + + <!-- Google Analytics Magic --> + <script type="text/javascript"> + var _gaq = _gaq || []; + _gaq.push(['_setAccount', 'UA-20226872-1']); + _gaq.push(['_setDomainName', 'apache.org']); + _gaq.push(['_trackPageview']); + + (function() { + var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; + ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; + var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); + })(); + </script> + + </head> + <body> + <!-- magical breadcrumbs --> + <div class="topnav"> + <div class="container"> + <ul class="breadcrumb"> + <li> + <div class="dropdown"> + <a data-toggle="dropdown" href="#">Apache Software Foundation <span class="caret"></span></a> + <ul class="dropdown-menu" role="menu" aria-labelledby="dLabel"> + <li><a href="http://www.apache.org";>Apache Homepage</a></li> + <li><a href="http://www.apache.org/licenses/";>License</a></li> + <li><a href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li> + <li><a href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li> + <li><a href="http://www.apache.org/security/";>Security</a></li> + </ul> + </div> + </li> + + <li><a href="http://mesos.apache.org";>Apache Mesos</a></li> + + + <li><a href="/documentation +/">Documentation +</a></li> + + + </ul><!-- /.breadcrumb --> + </div><!-- /.container --> + </div><!-- /.topnav --> + + <!-- navbar excitement --> +<div class="navbar navbar-default navbar-static-top" role="navigation"> + <div class="container"> + <div class="navbar-header"> + <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#mesos-menu" aria-expanded="false"> + <span class="sr-only">Toggle navigation</span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + <a class="navbar-brand" href="/"><img src="/assets/img/mesos_logo.png" alt="Apache Mesos logo"/></a> + </div><!-- /.navbar-header --> + + <div class="navbar-collapse collapse" id="mesos-menu"> + <ul class="nav navbar-nav navbar-right"> + <li><a href="/gettingstarted/">Getting Started</a></li> + <li><a href="/blog/">Blog</a></li> + <li><a href="/documentation/latest/">Documentation</a></li> + <li><a href="/downloads/">Downloads</a></li> + <li><a href="/community/">Community</a></li> + </ul> + </div><!-- /#mesos-menu --> + </div><!-- /.container --> +</div><!-- /.navbar --> + +<div class="content"> + <div class="container"> + <div class="row-fluid"> + <div class="col-md-4"> + <h4>If you're new to Mesos</h4> + <p>See the <a href="/gettingstarted/">getting started</a> page for more + information about downloading, building, and deploying Mesos.</p> + + <h4>If you'd like to get involved or you're looking for support</h4> + <p>See our <a href="/community/">community</a> page for more details.</p> + </div> + <div class="col-md-8"> + <h1>Master Options</h1> + +<h2>Required Flags</h2> + +<table class="table table-striped"> + <thead> + <tr> + <th width="30%"> + Flag + </th> + <th> + Explanation + </th> + </tr> + </thead> +<tr> + <td> + --quorum=VALUE + </td> + <td> +The size of the quorum of replicas when using <code>replicated_log</code> based +registry. It is imperative to set this value to be a majority of +masters i.e., <code>quorum > (number of masters)/2</code>. +<b>NOTE</b>: Not required if master is run in standalone mode (non-HA). + </td> +</tr> +<tr> + <td> + --work_dir=VALUE + </td> + <td> +Path of the master work directory. This is where the persistent +information of the cluster will be stored. Note that locations like +<code>/tmp</code> which are cleaned automatically are not suitable for the work +directory when running in production, since long-running masters could +lose data when cleanup occurs. (Example: <code>/var/lib/mesos/master</code>) + </td> +</tr> +<tr> + <td> + --zk=VALUE + </td> + <td> +ZooKeeper URL (used for leader election amongst masters). +May be one of: +<pre><code>zk://host1:port1,host2:port2,.../path +zk://username:password@host1:port1,host2:port2,.../path +file:///path/to/file (where file contains one of the above)</code></pre> +<b>NOTE</b>: Not required if master is run in standalone mode (non-HA). + </td> +</tr> +</table> + + +<h2>Optional Flags</h2> + +<table class="table table-striped"> + <thead> + <tr> + <th width="30%"> + Flag + </th> + <th> + Explanation + </th> + </tr> + </thead> +<tr> + <td> + --acls=VALUE + </td> + <td> +The value could be a JSON-formatted string of ACLs +or a file path containing the JSON-formatted ACLs used +for authorization. Path could be of the form <code>file:///path/to/file</code> +or <code>/path/to/file</code>. +<p/> +Note that if the flag <code>--authorizers</code> is provided with a value +different than <code>local</code>, the ACLs contents will be +ignored. +<p/> +See the ACLs protobuf in acls.proto for the expected format. +<p/> +Example: +<pre><code>{ + "register_frameworks": [ + { + "principals": { "type": "ANY" }, + "roles": { "values": ["a"] } + } + ], + "run_tasks": [ + { + "principals": { "values": ["a", "b"] }, + "users": { "values": ["c"] } + } + ], + "teardown_frameworks": [ + { + "principals": { "values": ["a", "b"] }, + "framework_principals": { "values": ["c"] } + } + ], + "set_quotas": [ + { + "principals": { "values": ["a"] }, + "roles": { "values": ["a", "b"] } + } + ], + "remove_quotas": [ + { + "principals": { "values": ["a"] }, + "quota_principals": { "values": ["a"] } + } + ], + "get_endpoints": [ + { + "principals": { "values": ["a"] }, + "paths": { "values": ["/flags"] } + } + ] +}</code></pre> + </td> +</tr> +<tr> + <td> + --agent_ping_timeout=VALUE, + <p/> + --slave_ping_timeout=VALUE + </td> + <td> +The timeout within which an agent is expected to respond to a +ping from the master. Agents that do not respond within +max_agent_ping_timeouts ping retries will be asked to shutdown. +<b>NOTE</b>: The total ping timeout (<code>agent_ping_timeout</code> multiplied by +<code>max_agent_ping_timeouts</code>) should be greater than the ZooKeeper +session timeout to prevent useless re-registration attempts. +(default: 15secs) + </td> +</tr> +<tr> + <td> + --agent_removal_rate_limit=VALUE + <p/> + --slave_removal_rate_limit=VALUE + </td> + <td> +The maximum rate (e.g., <code>1/10mins</code>, <code>2/3hrs</code>, etc) at which agents +will be removed from the master when they fail health checks. +By default, agents will be removed as soon as they fail the health +checks. The value is of the form <code>(Number of agents)/(Duration)</code>. + </td> +</tr> +<tr> + <td> + --agent_reregister_timeout=VALUE + <p/> + --slave_reregister_timeout=VALUE + </td> + <td> +The timeout within which an agent is expected to re-register. +Agents re-register when they become disconnected from the master +or when a new master is elected as the leader. Agents that do not +re-register within the timeout will be marked unreachable in the +registry; if/when the agent re-registers with the master, any +non-partition-aware tasks running on the agent will be terminated. +<b>NOTE</b>: This value has to be at least 10mins. (default: 10mins) + </td> +</tr> +<tr> + <td> + --allocation_interval=VALUE + </td> + <td> +Amount of time to wait between performing +(batch) allocations (e.g., 500ms, 1sec, etc). (default: 1secs) + </td> +</tr> +<tr> + <td> + --allocator=VALUE + </td> + <td> +Allocator to use for resource allocation to frameworks. +Use the default <code>HierarchicalDRF</code> allocator, or +load an alternate allocator module using <code>--modules</code>. +(default: HierarchicalDRF) + </td> +</tr> +<tr> + <td> + --[no-]authenticate_agents, + <p/> + --[no-]authenticate_slaves + </td> + <td> +If <code>true</code> only authenticated agents are allowed to register. +If <code>false</code> unauthenticated agents are also allowed to register. (default: false) + </td> +</tr> +<tr> + <td> + --[no-]authenticate_frameworks, + <p/> + --[no-]authenticate + </td> + <td> +If <code>true</code>, only authenticated frameworks are allowed to register. If +<code>false</code>, unauthenticated frameworks are also allowed to register. For +HTTP based frameworks use the <code>--authenticate_http_frameworks</code> flag. (default: false) + </td> +</tr> +<tr> + <td> + --[no-]authenticate_http_frameworks + </td> + <td> +If <code>true</code>, only authenticated HTTP based frameworks are allowed to +register. If <code>false</code>, HTTP frameworks are not authenticated. (default: false) + </td> +</tr> +<tr> + <td> + --authenticators=VALUE + </td> + <td> +Authenticator implementation to use when authenticating frameworks +and/or agents. Use the default <code>crammd5</code>, or +load an alternate authenticator module using <code>--modules</code>. (default: crammd5) + </td> +</tr> +<tr> + <td> + --authorizers=VALUE + </td> + <td> +Authorizer implementation to use when authorizing actions that +require it. +Use the default <code>local</code>, or +load an alternate authorizer module using <code>--modules</code>. +<p/> +Note that if the flag <code>--authorizers</code> is provided with a value +different than the default <code>local</code>, the ACLs +passed through the <code>--acls</code> flag will be ignored. +<p/> +Currently there is no support for multiple authorizers. (default: local) + </td> +</tr> +<tr> + <td> + --cluster=VALUE + </td> + <td> +Human readable name for the cluster, displayed in the webui. + </td> +</tr> +<tr> + <td> + --credentials=VALUE + </td> + <td> +Path to a JSON-formatted file containing credentials. +Path can be of the form <code>file:///path/to/file</code> or <code>/path/to/file</code>. +Example: +<pre><code>{ + "credentials": [ + { + "principal": "sherman", + "secret": "kitesurf" + } + ] +}</code></pre> + </td> +</tr> +<tr> + <td> + --fair_sharing_excluded_resource_names=VALUE + </td> + <td> +A comma-separated list of the resource names (e.g. 'gpus') that will be excluded +from fair sharing constraints. This may be useful in cases where the fair +sharing implementation currently has limitations. E.g. See the problem of +"scarce" resources: + <a href="http://www.mail-archive.com/dev@mesos.apache.org/msg35631.html";>msg35631</a> + <a href="https://issues.apache.org/jira/browse/MESOS-5377";>MESOS-5377</a> + </td> +</tr> +<tr> + <td> + --[no_]filter_gpu_resources + </td> + <td> +When set to true, this flag will cause the mesos master to filter all offers +from agents with GPU resources by only sending them to frameworks that opt into +the 'GPU_RESOURCES' framework capability. When set to false, this flag will +cause the master to not filter offers from agents with GPU resources, and +indiscriminately send them to all frameworks whether they set the +'GPU_RESOURCES' capability or not. This flag is meant as a temporary workaround +towards the eventual deprecation of the 'GPU_RESOURCES' capability. Please see +the following for more information: + <a href="https://www.mail-archive.com/dev@mesos.apache.org/msg37571.html";>msg37571</a> + <a href="https://issues.apache.org/jira/browse/MESOS-7576";>MESOS-7576</a> + </td> +</tr> +<tr> + <td> + --framework_sorter=VALUE + </td> + <td> +Policy to use for allocating resources between a given user's +frameworks. Options are the same as for <code>--user_sorter</code>. +(default: drf) + </td> +</tr> +<tr> + <td> + --http_framework_authenticators=VALUE + </td> + <td> +HTTP authenticator implementation to use when authenticating HTTP frameworks. +Use the <code>basic</code> authenticator or load an alternate HTTP authenticator +module using <code>--modules</code>. This must be used in conjunction with +<code>--authenticate_http_frameworks</code>. +<p/> +Currently there is no support for multiple HTTP authenticators. + </td> +</tr> +<tr> + <td> + --[no-]log_auto_initialize + </td> + <td> +Whether to automatically initialize the [replicated log](/documentation/latest/configuration/../replicated-log-internals/) +used for the registry. If this is set to false, the log has to be manually +initialized when used for the very first time. (default: true) + </td> +</tr> +<tr> + <td> + --master_contender=VALUE + </td> + <td> +The symbol name of the master contender to use. This symbol should exist in a +module specified through the <code>--modules</code> flag. Cannot be used in +conjunction with <code>--zk</code>. Must be used in conjunction with +<code>--master_detector</code>. + </td> +</tr> +<tr> + <td> + --master_detector=VALUE + </td> + <td> +The symbol name of the master detector to use. This symbol should exist in a +module specified through the <code>--modules</code> flag. Cannot be used in +conjunction with <code>--zk</code>. Must be used in conjunction with +<code>--master_contender</code>. + </td> +</tr> +<tr> + <td> + --max_agent_ping_timeouts=VALUE, + <p/> + --max_slave_ping_timeouts=VALUE + </td> + <td> +The number of times an agent can fail to respond to a +ping from the master. Agents that do not respond within +<code>max_agent_ping_timeouts</code> ping retries will be asked to shutdown. +(default: 5) + </td> +</tr> +<tr> + <td> + --max_completed_frameworks=VALUE + </td> + <td> +Maximum number of completed frameworks to store in memory. (default: 50) + </td> +</tr> +<tr> + <td> + --max_completed_tasks_per_framework=VALUE + </td> + <td> +Maximum number of completed tasks per framework to store in memory. (default: 1000) + </td> +</tr> +<tr> + <td> + --max_unreachable_tasks_per_framework=VALUE + </td> + <td> +Maximum number of unreachable tasks per framework to store in memory. (default: 1000) + </td> +</tr> +<tr> + <td> + --offer_timeout=VALUE + </td> + <td> +Duration of time before an offer is rescinded from a framework. +This helps fairness when running frameworks that hold on to offers, +or frameworks that accidentally drop offers. +If not set, offers do not timeout. + </td> +</tr> +<tr> + <td> + --rate_limits=VALUE + </td> + <td> +The value could be a JSON-formatted string of rate limits +or a file path containing the JSON-formatted rate limits used +for framework rate limiting. +Path could be of the form <code>file:///path/to/file</code> +or <code>/path/to/file</code>. +<p/> +See the RateLimits protobuf in mesos.proto for the expected format. +<p/> +Example: +<pre><code>{ + "limits": [ + { + "principal": "foo", + "qps": 55.5 + }, + { + "principal": "bar" + } + ], + "aggregate_default_qps": 33.3 +}</code></pre> + </td> +</tr> +<tr> + <td> + --recovery_agent_removal_limit=VALUE, + <p/> + --recovery_slave_removal_limit=VALUE + </td> + <td> +For failovers, limit on the percentage of agents that can be removed +from the registry *and* shutdown after the re-registration timeout +elapses. If the limit is exceeded, the master will fail over rather +than remove the agents. +This can be used to provide safety guarantees for production +environments. Production environments may expect that across master +failovers, at most a certain percentage of agents will fail +permanently (e.g. due to rack-level failures). +Setting this limit would ensure that a human needs to get +involved should an unexpected widespread failure of agents occur +in the cluster. +Values: [0%-100%] (default: 100%) + </td> +</tr> +<tr> + <td> + --registry=VALUE + </td> + <td> +Persistence strategy for the registry; available options are +<code>replicated_log</code>, <code>in_memory</code> (for testing). (default: replicated_log) + </td> +</tr> +<tr> + <td> + --registry_fetch_timeout=VALUE + </td> + <td> +Duration of time to wait in order to fetch data from the registry +after which the operation is considered a failure. (default: 1mins) + </td> +</tr> +<tr> + <td> + --registry_store_timeout=VALUE + </td> + <td> +Duration of time to wait in order to store data in the registry +after which the operation is considered a failure. (default: 20secs) + </td> +</tr> +<tr> + <td> + --roles=VALUE + </td> + <td> +A comma-separated list of the allocation roles that frameworks +in this cluster may belong to. This flag is deprecated; +if it is not specified, any role name can be used. + </td> +</tr> +<tr> + <td> + --[no-]root_submissions + </td> + <td> +Can root submit frameworks? (default: true) + </td> +</tr> +<tr> + <td> + --user_sorter=VALUE + </td> + <td> +Policy to use for allocating resources between users. May be one of: + dominant_resource_fairness (drf) (default: drf) + </td> +</tr> +<tr> + <td> + --webui_dir=VALUE + </td> + <td> +Directory path of the webui files/assets (default: /usr/local/share/mesos/webui) + </td> +</tr> +<tr> + <td> + --weights=VALUE + </td> + <td> +A comma-separated list of role/weight pairs of the form +<code>role=weight,role=weight</code>. Weights can be used to control the +relative share of cluster resources that is offered to different roles. This +flag is deprecated. Instead, operators should configure weights dynamically +using the <code>/weights</code> HTTP endpoint. + </td> +</tr> +<tr> + <td> + --whitelist=VALUE + </td> + <td> +Path to a file which contains a list of agents (one per line) to +advertise offers for. The file is watched and periodically re-read to +refresh the agent whitelist. By default there is no whitelist: all +machines are accepted. Path can be of the form +<code>file:///path/to/file</code> or <code>/path/to/file</code>. + </td> +</tr> +</table> + + +<h2>Network Isolator Flags</h2> + +<p><em>Available when configured with <code>--with-network-isolator</code>.</em></p> + +<table class="table table-striped"> + <thead> + <tr> + <th width="30%"> + Flag + </th> + <th> + Explanation + </th> + </tr> + </thead> +<tr> + <td> + --max_executors_per_agent=VALUE, + <p/> + --max_executors_per_slave=VALUE + </td> + <td> +Maximum number of executors allowed per agent. The network +monitoring/isolation technique imposes an implicit resource +acquisition on each executor (# ephemeral ports), as a result +one can only run a certain number of executors on each agent. + </td> +</tr> +</table> + + + </div> +</div> + + </div><!-- /.container --> +</div><!-- /.content --> + +<hr> + + + + <!-- footer --> + <div class="footer"> + <div class="container"> + <div class="col-md-4 social-blk"> + <span class="social"> + <a href="https://twitter.com/ApacheMesos"; + class="twitter-follow-button" + data-show-count="false" data-size="large">Follow @ApacheMesos</a> + <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script> + <a href="https://twitter.com/intent/tweet?button_hashtag=mesos"; + class="twitter-hashtag-button" + data-size="large" + data-related="ApacheMesos">Tweet #mesos</a> + <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script> + </span> + </div> + + <div class="col-md-8 trademark"> + <p>© 2012-2017 <a href="http://apache.org";>The Apache Software Foundation</a>. + Apache Mesos, the Apache feather logo, and the Apache Mesos project logo are trademarks of The Apache Software Foundation. + <p> + </div> + </div><!-- /.container --> + </div><!-- /.footer --> + + <!-- JS --> + <script src="//code.jquery.com/jquery-1.11.0.min.js" type="text/javascript"></script> + <script src="//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js" type="text/javascript"></script> + </body> +</html> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/container-image/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/container-image/index.html b/content/documentation/latest/container-image/index.html index de66522..9ead890 100644 --- a/content/documentation/latest/container-image/index.html +++ b/content/documentation/latest/container-image/index.html @@ -310,7 +310,7 @@ container credential is not supported yet (coming soon).</p> <p>Operators can either specify the flag as an absolute path pointing to the docker config file (need to manually configure <code>.docker/config.json</code> or <code>.dockercfg</code> on each agent), or specify the -flag as a JSON-formatted string. See <a href="/documentation/latest/./configuration/">configuration +flag as a JSON-formatted string. See <a href="/documentation/latest/./configuration/agent/">configuration documentation</a> for detail. For example:</p> <pre><code>--docker_config=file:///home/vagrant/.docker/config.json http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/docker-containerizer/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/docker-containerizer/index.html b/content/documentation/latest/docker-containerizer/index.html index 4bc4775..4817ab9 100644 --- a/content/documentation/latest/docker-containerizer/index.html +++ b/content/documentation/latest/docker-containerizer/index.html @@ -212,7 +212,7 @@ sandbox so docker cli will automatically pick up the config file.</p> config file for pulling images from private registries. We allow operators to specify a shared docker config file using an agent flag. This docker config file will be used to pull images from private -registries for all containers. See <a href="/documentation/latest/./configuration/">configuration +registries for all containers. See <a href="/documentation/latest/./configuration/agent/">configuration documentation</a> for detail. Operators can either specify the flag as an absolute path pointing to the docker config file (need to manually configure <code>.docker/config.json</code> or <code>.dockercfg</code> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/fetcher/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/fetcher/index.html b/content/documentation/latest/fetcher/index.html index 1f84ac2..49842e2 100644 --- a/content/documentation/latest/fetcher/index.html +++ b/content/documentation/latest/fetcher/index.html @@ -132,7 +132,7 @@ the input to the Mesos fetcher.</p> supports the HTTP, HTTPS, FTP and FTPS protocols. If the requested URI is based on some other protocol, then the fetcher tries to utilise a local Hadoop client and hence supports any protocol supported by the Hadoop client, e.g., HDFS, S3. -See the agent <a href="/documentation/latest/./configuration/">configuration documentation</a> +See the agent <a href="/documentation/latest/./configuration/agent/">configuration documentation</a> for how to configure the agent with a path to the Hadoop client.</p> <p>By default, each requested URI is downloaded directly into the sandbox directory http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/index.html b/content/documentation/latest/index.html index f6a9080..44ee1d9 100644 --- a/content/documentation/latest/index.html +++ b/content/documentation/latest/index.html @@ -130,7 +130,8 @@ <li><a href="/documentation/latest/./agent-recovery/">Agent Recovery</a> for doing seamless agent upgrades and allowing executors to survive <code>mesos-agent</code> crashes.</li> <li><a href="/documentation/latest/./authentication/">Authentication</a></li> <li><a href="/documentation/latest/./authorization/">Authorization</a></li> -<li><a href="/documentation/latest/./configuration/">Configuration</a> and <a href="/documentation/latest/./configuration-cmake/">CMake configuration</a> for command-line arguments.</li> +<li><a href="/documentation/latest/./cmake/">CMake</a> for details about using the new CMake build system.</li> +<li><a href="/documentation/latest/./configuration/">Configuration</a> for command-line arguments.</li> <li><a href="/documentation/latest/./container-image/">Container Image</a> for supporting container images in Mesos containerizer.</li> <li><a href="/documentation/latest/./container-volume/">Container Volume</a> for using container volumes.</li> <li><a href="/documentation/latest/./containerizers/">Containerizers</a> for containerizer overview and use cases. http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/logging/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/logging/index.html b/content/documentation/latest/logging/index.html index 1323882..c67307a 100644 --- a/content/documentation/latest/logging/index.html +++ b/content/documentation/latest/logging/index.html @@ -134,7 +134,8 @@ implement their own logging solution.</li> <p>The Mesos Master and Agent use the <a href="https://github.com/google/glog";>Google’s logging library</a>. For information regarding the command-line options used to configure this -library, see the <a href="/documentation/latest/./configuration/">configuration documentation</a>. +library, see the +<a href="/documentation/latest/./configuration/master-and-agent/#logging-options">configuration documentation</a>. Google logging options that are not explicitly mentioned there can be configured via environment variables.</p> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/latest/sandbox/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/sandbox/index.html b/content/documentation/latest/sandbox/index.html index 4d49525..bab2b59 100644 --- a/content/documentation/latest/sandbox/index.html +++ b/content/documentation/latest/sandbox/index.html @@ -287,7 +287,7 @@ After the delay, the files are deleted.</p> <p>Additionally, according to the <code>--disk_watch_interval</code> agent flag, files scheduled for garbage collection are pruned based on the available disk and the <code>--gc_disk_headroom</code> agent flag. -See <a href="/documentation/latest/./configuration/#gc_disk_headroom">the formula here</a>.</p> +See <a href="/documentation/latest/./configuration/agent/#gc_disk_headroom">the formula here</a>.</p> </div> </div> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/logging/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/logging/index.html b/content/documentation/logging/index.html index 7597828..00800c5 100644 --- a/content/documentation/logging/index.html +++ b/content/documentation/logging/index.html @@ -134,7 +134,8 @@ implement their own logging solution.</li> <p>The Mesos Master and Agent use the <a href="https://github.com/google/glog";>Google’s logging library</a>. For information regarding the command-line options used to configure this -library, see the <a href="/documentation/latest/./configuration/">configuration documentation</a>. +library, see the +<a href="/documentation/latest/./configuration/master-and-agent/#logging-options">configuration documentation</a>. Google logging options that are not explicitly mentioned there can be configured via environment variables.</p> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/documentation/sandbox/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/sandbox/index.html b/content/documentation/sandbox/index.html index 70a67c9..48b537e 100644 --- a/content/documentation/sandbox/index.html +++ b/content/documentation/sandbox/index.html @@ -287,7 +287,7 @@ After the delay, the files are deleted.</p> <p>Additionally, according to the <code>--disk_watch_interval</code> agent flag, files scheduled for garbage collection are pruned based on the available disk and the <code>--gc_disk_headroom</code> agent flag. -See <a href="/documentation/latest/./configuration/#gc_disk_headroom">the formula here</a>.</p> +See <a href="/documentation/latest/./configuration/agent/#gc_disk_headroom">the formula here</a>.</p> </div> </div> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a5fb0e1c/content/sitemap.xml ---------------------------------------------------------------------- diff --git a/content/sitemap.xml b/content/sitemap.xml index 14fc059..9d974a7 100644 --- a/content/sitemap.xml +++ b/content/sitemap.xml @@ -16069,6 +16069,14 @@ <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> <url> + <loc>http://mesos.apache.org/documentation/latest/cmake-examples/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> + <loc>http://mesos.apache.org/documentation/latest/cmake/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> <loc>http://mesos.apache.org/documentation/latest/design-docs/</loc> <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> @@ -16189,6 +16197,30 @@ <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> <url> + <loc>http://mesos.apache.org/documentation/latest/configuration/cmake/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> + <loc>http://mesos.apache.org/documentation/latest/configuration/master-and-agent/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> + <loc>http://mesos.apache.org/documentation/latest/configuration/master/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> + <loc>http://mesos.apache.org/documentation/latest/configuration/autotools/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> + <loc>http://mesos.apache.org/documentation/latest/configuration/libprocess/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> + <loc>http://mesos.apache.org/documentation/latest/configuration/agent/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> <loc>http://mesos.apache.org/documentation/latest/oversubscription/</loc> <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> @@ -16249,10 +16281,6 @@ <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> <url> - <loc>http://mesos.apache.org/documentation/latest/configuration-cmake/</loc> - <lastmod>2017-10-11T00:00:00+00:00</lastmod> - </url> - <url> <loc>http://mesos.apache.org/documentation/latest/windows/</loc> <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> @@ -16885,6 +16913,14 @@ <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> <url> + <loc>http://mesos.apache.org/documentation/cmake-examples/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> + <loc>http://mesos.apache.org/documentation/cmake/</loc> + <lastmod>2017-10-11T00:00:00+00:00</lastmod> + </url> + <url> <loc>http://mesos.apache.org/documentation/design-docs/</loc> <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> @@ -17021,10 +17057,6 @@ <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url> <url> - <loc>http://mesos.apache.org/documentation/configuration-cmake/</loc> - <lastmod>2017-10-11T00:00:00+00:00</lastmod> - </url> - <url> <loc>http://mesos.apache.org/documentation/windows/</loc> <lastmod>2017-10-11T00:00:00+00:00</lastmod> </url>
![http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/](http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/){kind=link}