Re: mesos-master resource offer details

Hi, Haripriya. >1. I am trying to see the details of the resource offer made by the mesos master. I can see in the logs that there are 5 resource offers made but I am not sure where to get the details of the resource offers - the cpu, memory etc. You could print offer details in your framework

Recommended way to discover current master

My framework knows the list of zookeeper hosts and the list of mesos master hosts. I can think of a few ways for the framework to figure out which host is the current master. What would be the best? Should I check in zookeeper directly? Does the mesos library expose an interface to discover the

Re: Recommended way to discover current master

> On Aug 31, 2015, at 10:25 AM, Philip Weaver wrote: > > My framework knows the list of zookeeper hosts and the list of mesos master > hosts. > > I can think of a few ways for the framework to figure out which host is the > current master. What would be the best?

Re: Recommended way to discover current master

The easiest way is via accessing directly Zookeeper - as you don't need to know a priori the list of Masters; if you do, however, hitting any one of them will redirect (302) to the current Leader. If you would like to see an example of how to retrieve that info from ZK, I have written about it

Re: Recommended way to discover current master

Excellent, thank you both! On Mon, Aug 31, 2015 at 10:39 AM, Marco Massenzio wrote: > The easiest way is via accessing directly Zookeeper - as you don't need to > know a priori the list of Masters; if you do, however, hitting any one of > them will redirect (302) to the

Re: Recommended way to discover current master

It's also worth noting the existence of the `mesos-resolve` binary, which can turn a canonical Mesos ZK string into the leading master location. -- Connor > On Aug 31, 2015, at 10:39, Marco Massenzio wrote: > > The easiest way is via accessing directly Zookeeper - as you

Re: Mesos-master complains about quorum being a duplicate flag on CoreOS

Thanks for following up, glad we figured it out. IMO the current behavior (and the error message) are non-intuitive and I've filed a Jira[0] to address that. [0] https://issues.apache.org/jira/browse/MESOS-3340 *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com

mesos-slave crashing with CHECK_SOME

Hi all, We are running Mesos 0.22.1 on CentOS 6 and are hitting some frequent mesos-slave crashes when we try to upgrade our Marathon applications. The crash happens when Marathon deploys a new version of an application and stops a running task. The error in the Mesos logs is:

Re: [VOTE] Release Apache Mesos 0.24.0 (rc1)

Hi Dario, Can you test with "curl --no-buffer" option? Looks like your stdout might be line-buffered. The reason we used record-io formatting is to be consistent in how we stream protobuf and json encoded data. On Fri, Aug 28, 2015 at 2:04 PM, wrote: > Anand, > > thanks

Re: mesos-slave crashing with CHECK_SOME

On Aug 31, 2015, at 11:54 AM, Scott Rankin wrote: > > tag=mesos-slave[12858]: F0831 09:37:29.838184 12898 slave.cpp:3354] > CHECK_SOME(os::touch(path)): Failed to open file: No such file or directory I reported a similar bug a while back:

Re: Recommended way to discover current master

If you have mesos DNS there, access leader.mesos :) Sent from Christos' phone. > On Aug 31, 2015, at 10:25 AM, Philip Weaver wrote: > > My framework knows the list of zookeeper hosts and the list of mesos master > hosts. > > I can think of a few ways for the

mesos-master resource offer details

Hello, I'm having trouble with some basic details: 1. I am trying to see the details of the resource offer made by the mesos master. I can see in the logs that there are 5 resource offers made but I am not sure where to get the details of the resource offers - the cpu, memory etc. 2. How can I

Re: Mesos-master complains about quorum being a duplicate flag on CoreOS

Command line flags are parsed using stout/flags.hpp[0] and the FlagsBase class is derived in mesos::internal::master::Flags (see src/master/flags.hpp[1]). I am not sure why you are seeing that behavior on CoreOS, but I'd be curious to know what happens if you omit the --quorum when you start

How is task mem usage calculated

In the master UI for task status there's an allocated and used value for the task. Allocated seems to correspond to the amount requested by the scheduler but I can't seem to figure out how Used is calculated. For mesos command tasks it doesn't look like it matches virtual or real mem usage in