You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by gi...@apache.org on 2018/11/19 21:23:08 UTC
[mesos-site] branch asf-site updated: Updated the website built
from mesos SHA: 60a8577.
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/mesos-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 66394a1 Updated the website built from mesos SHA: 60a8577.
66394a1 is described below
commit 66394a14063e3695e7dbef9005ea106c565b1568
Author: jenkins <bu...@apache.org>
AuthorDate: Mon Nov 19 21:23:06 2018 +0000
Updated the website built from mesos SHA: 60a8577.
---
.../documentation/app-framework-development-guide/index.html | 10 ++++++++--
.../latest/app-framework-development-guide/index.html | 10 ++++++++--
2 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/content/documentation/app-framework-development-guide/index.html b/content/documentation/app-framework-development-guide/index.html
index 73559d3..887ab12 100644
--- a/content/documentation/app-framework-development-guide/index.html
+++ b/content/documentation/app-framework-development-guide/index.html
@@ -177,12 +177,18 @@ not receive enough resources.</li>
a “job”/“service”/etc within a multi-tenant scheduler) needs a certain amount of
resources guaranteed to it, setting a quota ensures that Mesos will try its best
to allocate to satisfy the guarantee.</li>
+<li><strong>Set the minimum allocatable resources</strong>: Once quota is used, the
+<code>--min_allocatable_resources</code> flag should be set
+(e.g. <code>--min_allocatable_resources=cpus:1,mem:32:disk:32</code>) to prevent offers
+that are missing cpu, memory, or disk
+(see <a href="https://issues.apache.org/jira/browse/MESOS-8935">MESOS-8935</a>).</li>
<li><strong>Consider enabling the random sorter</strong>: Depending on the use case, DRF can prove
problematic in that it will try to allocate to frameworks with a low share of the
cluster and penalize frameworks with a high share of the cluster. This can lead
to offer starvation for higher share frameworks. To allocate using a weighted
-random uniform distribution instead of fair sharing, set <code>--role-sorter=random</code>
-and <code>--framework_sorter=random</code>.</li>
+random uniform distribution instead of fair sharing, set <code>--role_sorter=random</code>
+and <code>--framework_sorter=random</code> (see
+<a href="https://issues.apache.org/jira/browse/MESOS-8936">MESOS-8936</a>).</li>
</ol>
diff --git a/content/documentation/latest/app-framework-development-guide/index.html b/content/documentation/latest/app-framework-development-guide/index.html
index b066e9e..9a28a63 100644
--- a/content/documentation/latest/app-framework-development-guide/index.html
+++ b/content/documentation/latest/app-framework-development-guide/index.html
@@ -177,12 +177,18 @@ not receive enough resources.</li>
a “job”/“service”/etc within a multi-tenant scheduler) needs a certain amount of
resources guaranteed to it, setting a quota ensures that Mesos will try its best
to allocate to satisfy the guarantee.</li>
+<li><strong>Set the minimum allocatable resources</strong>: Once quota is used, the
+<code>--min_allocatable_resources</code> flag should be set
+(e.g. <code>--min_allocatable_resources=cpus:1,mem:32:disk:32</code>) to prevent offers
+that are missing cpu, memory, or disk
+(see <a href="https://issues.apache.org/jira/browse/MESOS-8935">MESOS-8935</a>).</li>
<li><strong>Consider enabling the random sorter</strong>: Depending on the use case, DRF can prove
problematic in that it will try to allocate to frameworks with a low share of the
cluster and penalize frameworks with a high share of the cluster. This can lead
to offer starvation for higher share frameworks. To allocate using a weighted
-random uniform distribution instead of fair sharing, set <code>--role-sorter=random</code>
-and <code>--framework_sorter=random</code>.</li>
+random uniform distribution instead of fair sharing, set <code>--role_sorter=random</code>
+and <code>--framework_sorter=random</code> (see
+<a href="https://issues.apache.org/jira/browse/MESOS-8936">MESOS-8936</a>).</li>
</ol>