Re: Checking success of resource reservations

Please try "curl -s http://mesos_master:5050/roles | python -m json.tool" to get roles's info including reservation. Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform OpenSource Technology, STG, IBM GCG +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me On Sat, Apr 16,

Re: Framework taking default resources even though a role is specified

Which version are you using? For your requirement, I think you can try Quota; currently, the resources beyond quota will not offer to the framework whose quota satisfied. Quota will also include reserved resources. Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform OpenSource Te

Re: Framework taking default resources even though a role is specified

You can try setting constraints on tasks in both Chronos and marathon that will limit deployment to only a certain set of nodes.  Sent from Outlook for iPhone On Fri, Apr 15, 2016 at 1:35 PM -0700, "June Taylor" wrote: Evan, I'm not sure about it. We're new to the Mesos system and

Re: Framework taking default resources even though a role is specified

Evan, I'm not sure about it. We're new to the Mesos system and still learning. We want to be able to classify resources so that our developers can run tasks against them easily, without using more than they are permitted. It seemed like resource roles were the appropriate solution, but they may no

Re: Framework taking default resources even though a role is specified

My understanding is that your framework would have to know not to accept offers for * resources. Marathon has an option to specify which roles to accept for a particular app, and has command line options for controlling the default. Maybe pyspark has something similar? On Fri, Apr 15, 2016 at 1:24

Re: Framework taking default resources even though a role is specified

Yep - we're waiting for it. Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Fri, Apr 15, 2016 at 3:23 PM, Anand Mazumdar wrote: > FWIW, we recently fixed `mesos-execute` (command scheduler) to add support > for roles. It should be available in t

Re: Framework taking default resources even though a role is specified

FWIW, we recently fixed `mesos-execute` (command scheduler) to add support for roles. It should be available in the next release (0.29). https://issues.apache.org/jira/browse/MESOS-4744 -anand > On Apr 15, 2016, at 11:41 AM, June Taylor wrote

Re: Error on Teardown attempt: Framework is not connected via HTTP

The `py-spark` framework looks to be driver based i.e. it uses the `MesosSchedulerDriver` underneath. You would need to use the `/teardown` endpoint that takes in the `frameworkId`as a query parameter for tearing it down. For more details, see: http://mesos.apache.org/documentation/latest/endpo

Re: Error on Teardown attempt: Framework is not connected via HTTP

That's not the endpoint you want (that's for frameworks to use). You want /teardown endpoint (that's for operators).

Error on Teardown attempt: Framework is not connected via HTTP

We're getting the highlighted error message returned when attempting to tear down a framework on our cluster: june@cluster:~$ mesos frameworks ID NAMEHOST ACTIVE TASKS CPU MEM DISK 0c540ad0-a050-4c20-82df-7bd14ce95f5

Checking success of resource reservations

Hi everyone, I am making resource reservations and creating persistent volumes through the operator HTTP endpoints on v0.28.0. In order to see if the requests went through, the docs ( http://mesos.apache.org/documentation/latest/reservation/) say to check at the appropriate slave's /state endpoint

Re: Framework taking default resources even though a role is specified

Ken, Thanks for your reply. Is there a way to ensure a framework only receives the reserved resources? I would go ahead and take everything out of the * role, however, the 'mesos-execute' command doesn't support specifying a role, so that's the only way we can currently get mesos-execute to co-e

Re: Framework taking default resources even though a role is specified

The framework with role “production” will receive production resources and * resources All other frameworks (assuming no role) will only receive * resources ken > On Apr 15, 2016, at 11:38 AM, June Taylor wrote: > > We have a small cluster with 3 nodes in the * resource role default, and 3 >

Framework taking default resources even though a role is specified

We have a small cluster with 3 nodes in the * resource role default, and 3 nodes in a "production" resource role. Starting up a framework which requests "production" properly executes on the expected nodes, however, today we noticed that this job also started up executors under the * resource role

Re: Prometheus Exporters on Marathon

Thanks for the tip - I am not familiar with Golang and just installed whatever came from Ubuntu's packages. I see that is 1.2.1, so I will check out a newer version. Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Fri, Apr 15, 2016 at 8:36 AM, Dic

Re: Prometheus Exporters on Marathon

You are probably building on an older version of Golang - I think the Timeout attribute was added to http.Client around 1.5 or 1.6? On 15 April 2016 at 13:56, June Taylor wrote: > David, > > Thanks for the assistance. How did you get the mesos-exporter installed? > When I tried the instructions f

Re: Pyspark Cluster Mode

Pradeep, Thanks for the assistance! We'll be trying this out and I'll certainly let you know if we have questions. Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Fri, Apr 15, 2016 at 6:50 AM, Pradeep Chhetri < pradeep.chhetr...@gmail.com> wrote:

Re: Prometheus Exporters on Marathon

David, Thanks for the assistance. How did you get the mesos-exporter installed? When I tried the instructions from github.com/mesosphere/mesos-exporter, I got this error: june@-cluster:~$ go get github.com/mesosphere/mesos-exporter # github.com/mesosphere/mesos-exporter gosrc/src/github.com/mesos

Re: Pyspark Cluster Mode

Hi June, Here is the spark marathon configuration you were asking: https://gist.github.com/pradeepchhetri/df6b71580a9f107378ffebc789d805ac I have included the script to start MesosClusterDispatcher too in the above gist I would suggest you to use this Dockerfile as the reference for building spa

Re: Mesos Clusters on different Network

Maybe i found a solution is an openstack isshe. Probably i need jus to use the same virtual router for both netwoks. I will keep you updated Il 15/apr/2016 10:30, "Stefano Bianchi" ha scritto: > Hi > > I already asked this question but idecided to open a new topic since where > i wrote before wer

Re: Prometheus Exporters on Marathon

Sure. there is not a lot to it though. So we have simple service file like this /usr/lib/systemd/system/mesos_exporter.service ``` [Unit] Description=Prometheus mesos exporter [Service] EnvironmentFile=-/etc/sysconfig/mesos_exporter ExecStart=/usr/bin/mesos_exporter $OPTIONS Restart=on-failure `

Mesos Clusters on different Network

Hi I already asked this question but idecided to open a new topic since where i wrote before were not the correspondent topic. So, as many of you have already understood, i'm working on openstack, where there is not a DNS. I have made 2 networks, NetA and NetB, on each of them there is a mesos cl