[jira] [Assigned] (MESOS-9625) Make `DiskProfileAdaptor` agnostic to CSI spec version.
[
https://issues.apache.org/jira/browse/MESOS-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chun-Hung Hsiao reassigned MESOS-9625:
--
Assignee: Chun-Hung Hsiao
> Make `DiskProfileAdaptor` agnostic to CSI spec version.
> ---
>
> Key: MESOS-9625
> URL: https://issues.apache.org/jira/browse/MESOS-9625
> Project: Mesos
> Issue Type: Task
> Components: storage
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
>Priority: Blocker
> Labels: mesosphere, mesosphere-dss-ga, storage
>
> To support multiple CSI versions, the {{DiskProfileAdaptor}} module needs to
> be decoupled from CSI version. Mainly, we'll have to introduce a
> version-agnostic {{VolumeCapability}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-4719) Add allocator metric for number of offers each role / framework received.
[ https://issues.apache.org/jira/browse/MESOS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796550#comment-16796550 ] Gastón Kleiman commented on MESOS-4719: --- [~vinodkone] we currently have per-framework metrics for the number of offers that were sent, but we don't have the corresponding per-role metrics. > Add allocator metric for number of offers each role / framework received. > - > > Key: MESOS-4719 > URL: https://issues.apache.org/jira/browse/MESOS-4719 > Project: Mesos > Issue Type: Improvement > Components: allocation >Reporter: Benjamin Bannier >Priority: Major > Labels: mesosphere > > A counter for the number of allocations to a framework can be used to monitor > allocation progress, e.g., when agents are added to a cluster, and as other > frameworks are added or removed. > Currently, an offer by the hierarchical allocator to a framework consists of > a list of resources on possibly many agents. Resources might be offered in > order to satisfy outstanding quota or for fairness. To capture allocations on > fine granularity we should not count the number of offers, but instead the > pieces making up that offer, as such a metric would better resolve the effect > of changes (e.g., adding/removing a framework). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-4719) Add allocator metric for number of offers each role / framework received.
[ https://issues.apache.org/jira/browse/MESOS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796509#comment-16796509 ] Vinod Kone commented on MESOS-4719: --- [~greggomann] Don't we have this now? cc [~gkleiman] > Add allocator metric for number of offers each role / framework received. > - > > Key: MESOS-4719 > URL: https://issues.apache.org/jira/browse/MESOS-4719 > Project: Mesos > Issue Type: Improvement > Components: allocation >Reporter: Benjamin Bannier >Priority: Major > Labels: mesosphere > > A counter for the number of allocations to a framework can be used to monitor > allocation progress, e.g., when agents are added to a cluster, and as other > frameworks are added or removed. > Currently, an offer by the hierarchical allocator to a framework consists of > a list of resources on possibly many agents. Resources might be offered in > order to satisfy outstanding quota or for fairness. To capture allocations on > fine granularity we should not count the number of offers, but instead the > pieces making up that offer, as such a metric would better resolve the effect > of changes (e.g., adding/removing a framework). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-9500) spark submit with docker image on mesos cluster fails.
[ https://issues.apache.org/jira/browse/MESOS-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796507#comment-16796507 ] Vinod Kone commented on MESOS-9500: --- [~atheethkaup] Can you paste all the relevant agent log lines related to this task? It's hard to tell from just the line you posted above. We need log lines from the task launch all the way to task failing. > spark submit with docker image on mesos cluster fails. > -- > > Key: MESOS-9500 > URL: https://issues.apache.org/jira/browse/MESOS-9500 > Project: Mesos > Issue Type: Bug > Components: docker >Affects Versions: 1.7.0 >Reporter: atheeth kaup >Priority: Critical > > We have 3 node cluster with mesos(V 1.7), spark 2.4 and docker 18.06.1 > installed. one is master and other two are agents. while doing spark submit > job fails. UI shows only one task(Driver) launching on one of the slaves in > the failed state. > > command: > spark-submit \ > --master mesos://.32:7077 \ > --deploy-mode cluster \ > --class com.learning.spark.WordCount \ > --conf > spark.mesos.executor.docker.image=mesosphere/spark:2.4.0-2.2.1-3-hadoop-2.7 \ > --conf spark.master.rest.enabled=true \ > /home/mapr/mesos/wordcount.jar hdfs://***.36:8020/user/mapr/sparkL/input.txt > hdfs://***.36:8020/user/output > > Error in one of the Logs: > > Running on machine: **-i0058 > Log line format: [IWEF]mmdd hh:mm:ss.uu threadid > [file:line|file://line/]] msg > W1221 16:51:23.857431 17978 state.cpp:478] Failed to find executor forked pid > file > '/home/**/mesos/mesos-1.7.0/build/workDir/meta/slaves/822a5d52-b8ba-459f-ade2-7f3a2ebd240f-S0/frameworks/77c39bdf-09e3-4cb9-9026-21e900d08318-0007/executors/driver-20181221112019-0006/runs/7c1399ca-4e0a-4bd9-b02e-9c5ca3854c77/pids/forked.pid' > > Below is the only property that we have set on all the nodes and have started > the dispatcher: > *export MESOS_NATIVE_JAVA_LIBRARY=/usr/local/libmesos.so* > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-6874) Agent silently ignores FS isolation when protobuf is malformed
[
https://issues.apache.org/jira/browse/MESOS-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796412#comment-16796412
]
Benno Evers commented on MESOS-6874:
{noformat}
commit 93aca1eb0efcec941e19e976f683a35ecd9a840b
Author: Andrei Sekretenko
Date: Tue Mar 19 18:55:55 2019 +0100
Validated the match between Type and *Infos in the ContainerInfo.
[...]
{noformat}
> Agent silently ignores FS isolation when protobuf is malformed
> --
>
> Key: MESOS-6874
> URL: https://issues.apache.org/jira/browse/MESOS-6874
> Project: Mesos
> Issue Type: Bug
> Components: containerization
>Affects Versions: 1.1.0
>Reporter: Michael Gummelt
>Assignee: Andrei Sekretenko
>Priority: Minor
> Labels: foundations, newbie
> Time Spent: 40m
> Remaining Estimate: 0h
>
> cc [~vinodkone]
> I accidentally set my Mesos ContainerInfo to include a DockerInfo instead of
> a MesosInfo:
> {code}
> executorInfoBuilder.setContainer(
> Protos.ContainerInfo.newBuilder()
> .setType(Protos.ContainerInfo.Type.MESOS)
> .setDocker(Protos.ContainerInfo.DockerInfo.newBuilder()
>
> .setImage(podSpec.getContainer().get().getImageName()))
> {code}
> I would have expected a validation error before or during containerization,
> but instead, the agent silently decided to ignore filesystem isolation
> altogether, and launch my executor on the host filesystem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-9651) Design for docker registry v2 schema2 basic support.
[ https://issues.apache.org/jira/browse/MESOS-9651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone reassigned MESOS-9651: - Assignee: Qian Zhang > Design for docker registry v2 schema2 basic support. > > > Key: MESOS-9651 > URL: https://issues.apache.org/jira/browse/MESOS-9651 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Gilbert Song >Assignee: Qian Zhang >Priority: Major > Labels: containerization > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MESOS-9292) Rejected quotas request error messages should specify which resources were overcommitted.
[
https://issues.apache.org/jira/browse/MESOS-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler reassigned MESOS-9292:
--
Assignee: Benjamin Mahler
Sprint: Resource Mgmt RI12 Sp 42
> Rejected quotas request error messages should specify which resources were
> overcommitted.
> -
>
> Key: MESOS-9292
> URL: https://issues.apache.org/jira/browse/MESOS-9292
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
>Reporter: Benno Evers
>Assignee: Benjamin Mahler
>Priority: Major
> Labels: multitenancy
>
> If we reject a quota request due to not having enough available resources, we
> fail with the following error:
> {noformat}
> Not enough available cluster capacity to reasonably satisfy quota
> request; the force flag can be used to override this check
> {noformat}
> but we don't print *which* resource was not available. This can be confusing
> to operators when the quota was attempted to be set for multiple resources at
> once.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
