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

+1 (non-binding) All tests (including ROOT) pass on Ubuntu 14.04 All tests pass on CentOS 7.1; ROOT tests cause 1 failure: [ FAILED ] 1 test, listed below: [ FAILED ] CgroupsAnyHierarchyMemoryPressureTest.ROOT_IncreaseRSS $ cat /etc/centos-release CentOS Linux release 7.1.1503 (Core) This

Re: mesos-master resource offer details

ejected. I am trying to debug the reason as to why the resource >>>> offer is being rejected. >>>> >>>> On Tue, Sep 1, 2015 at 10:00 AM, haosdent <haosd...@gmail.com> wrote: >>>> >>>>> Yes, currently only print number for offers i

Re: mesos-master resource offer details

r is >>>>> being rejected. I am trying to debug the reason as to why the resource >>>>> offer is being rejected. >>>>> >>>>> On Tue, Sep 1, 2015 at 10:00 AM, haosdent <haosd...@gmail.com> wrote: >>>>> >>>>>> Yes, currently o

Re: mesos-slave crashing with CHECK_SOME

I 100% agree with your philosophy here, and I suspect it's something shared in the Mesos community. I just think that we can restrict the domain of the failure to a smaller reasonable window -- once you are in the context of "I am doing work to launch a specific task", there is a well defined

Re: mesos-master resource offer details

es, currently only print number for offers in mesos code in default >>>> log level. If you want get more details about it, you could start with set >>>> environment variable GLOG_v2=1 Then you should got some similar message >>>> like this: >>>> &g

Re: mesos-slave crashing with CHECK_SOME

If could show the content of path in CHECK_SOME, it would more easy to debug here. According the log in https://groups.google.com/forum/#!topic/marathon-framework/oKXhfQUcoMQ and 0.22.1 code: const string& path = paths::getExecutorSentinelPath( metaDir, info.id(), framework->id,

Re: mesos-master resource offer details

rce offer is >>>>> accepted and mesos-master then allocates the cpu. In my case, the offer is >>>>> being rejected. I am trying to debug the reason as to why the resource >>>>> offer is being rejected. >>>>> >>>>> On Tue, Se

Re: mesos-slave crashing with CHECK_SOME

Hi Scott, I wonder if you can try the latest Mesos and see if you can repro this? And if it is can you put down the example task and steps? I couldn't see disk full in your slave log so I'm not sure if it's exactly the same problem of MESOS-2684. Tim On Wed, Sep 2, 2015 at 5:15 AM, Scott

Re: Prepping for next release

I'd be in favor of setting that flag to Java 7 as well - just because classes are compiled in Java 6 format doesn't mean the standard library classes they reference will be available on Java 6 - your compiler classpath contains Java 7's rt.jar, which contains classes that don't exist in Java 6's

How does mesos determine how much memory on a node is available for offer?

I have 3 CoreOS nodes running in vagrant. Mesos is run natively (not in docker containers). There is 1 master/slave and 2 slaves. If I ssh into one of my slaves and run free -m, I see: Total: 2005 Used 1342 Free 662 Shares 273 Buffers 13 Cached 1210 In the mesos web-ui, I see that the slave

Re: How does mesos determine how much memory on a node is available for offer?

In case you don’t specify the resources via “—resources” flag when you start your agent, it picks up the default values. (Example: --resources="cpus:4;mem:1024;disk:2”) The default value for memory is here: https://github.com/apache/mesos/blob/master/src/slave/constants.cpp#L46

Re: How does mesos determine how much memory on a node is available for offer?

There seems to be some dynamicness to it. I just bumped the memory for each VM up to 2.5GB and now mesos is offering 1.5GB on it's slave. Is there some percentage value that I can set so that more memory is available to mesos? On 3/09/2015 11:23 AM, Anand Mazumdar wrote: In case you don’t

API client libraries

Hi folks, Now that the v1 scheduler HTTP API (beta) is on the verge of being released, I wanted to open up the discussion about client libraries for the API. Mainly around support and home for the libs. One idea is that, going forward, the only supported client library would be C++ library which

Re: API client libraries

Thanks for bringing this up, Vinod! We have to make sure that there are reference library implementations for at least Python, Java, and Go. They may end up being owned and maintained by the community, but I feel that Mesos developers should at least kickstart the process and incubate those

Re: Apache Mesos Community Sync

We'll have the next community sync tomorrow (Sept 3rd) at 3 PM PST. Please add items to agenda . On Wed, Aug 5, 2015 at 4:12 PM, Vinod Kone wrote: > We'll have

Re: mesos-slave crashing with CHECK_SOME

@Steven - agreed! As mentioned, if we can reduce the "footprint of unnecessary CHECKs" (so to speak) I'm all for it - let's document and add Jiras for that, by all means. @Scott - LoL: you certainly didn't; I was more worried my email would ;-) Thanks, guys! *Marco Massenzio* *Distributed

Help us review #MesosCon Europe 2015 proposals

A total of 65 proposals were submitted for #MesosCon Europe. Similar to previous MesosCon events, the program committee is opening these proposals up for community review/feedback to better-inform our decisions about what should be included in the program. In order to make it easier to review a

Re: API client libraries

On Wed, Sep 2, 2015 at 11:49 AM, Vinod Kone wrote: > --> Might be a step backward because we would be officially dropping > support for Java and Python. This is probably a good thing? > s/officially dropping support/dropping official support/

Re: API client libraries

@ Vinod:: An excellent idea as the code bases mature. It will force clear delineation of functionality and allow those 'other language" experts to define their codes for Mesos more clearly. @ Artem:: Another excellent point. The mesos "core team" will have to still work with the other

Re: mesos-slave crashing with CHECK_SOME

Hi Marco, I certainly don’t want to start a flame war, and I actually realized after I added my comment to MESOS-2684 that it’s not quite the same thing. As far as I can tell, in our situation, there’s no underlying disk issue. It seems like this is some sort of race condition (maybe?) with