Re: mesos-master resource offer details

Well, the log you mentioned above is when the resource 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, Sep 1, 2015 at 10:00 AM, haosdent

Re: mesos-master resource offer details

Yes, 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: I0902 00:55:17.465920 143396864 hierarchical.hpp:935] Allocating

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

Okay, thanks! On 01.09.2015, at 20:57, Benjamin Mahler wrote: >> One more question. From the Mesos code it doesn’t look like events are being >> split or combined, so given I have a client that gives me access to the >> individual chunks, is it safe to assume that

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

Hey guys, just a quick note to bring back the conversation on track to the 0.24-RC1 release. Is my understanding correct that there are currently no binding -1's? @Vinod: what do you think, are we good to release? Thanks! *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com

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

Cool - I'll ping Joseph on that one. (the -1 from Nik was related to the known ROOT test issues that -if memory serves- we agreed were non-blocking: I'll follow up with him too) *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com * On Tue, Sep 1, 2015 at

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

Thanks for the nudge Marco. There was a binding -1 from Niklas. I'm planning to cut an RC2. The cherry picks I've selected so far are in MESOS-2562 . The only one I'm currently waiting on to get a resolution for is

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

My only concern is that if we decide to change the protobuf -> json conversion for int64 (from json number to string), we should do that in the scheduler http api as well (Resource protobuf uses int64 for ports). But since the scheduler http api is labeled beta for 0.24, we can still change the

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

> > One more question. From the Mesos code it doesn’t look like events are > being split or combined, so given I have a client that gives me access to > the individual chunks, is it safe to assume that each chunk contains > exactly one event? Because that would make parsing the events a lot easier

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

Hi Vinod, thanks for the explanation, I got it now. Thanks, Dario > On 31.08.2015, at 23:47, Vinod Kone wrote: > > I think you might be confused with the HTTP chunked encoding and RecordIO > encoding. Most HTTP client libraries dechunk the stream before presenting it >

Re: Prepping for next release

I'm generally in favor of dropping support for JDK6 as it's been end-of-life for years. On Tue, Sep 1, 2015 at 4:46 PM, Vinod Kone wrote: > +user > > So looks like this issue is related to JDK6 and not my maven password > settings. > > Related ASF ticket:

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

Awesome - we'll be running RC2 through our CI env and let you know the outcome soon as we know. Thanks! *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com * On Tue, Sep 1, 2015 at 11:42 AM, Vinod Kone wrote: > My only concern is

Re: Prepping for next release

+user So looks like this issue is related to JDK6 and not my maven password settings. Related ASF ticket: https://issues.apache.org/jira/browse/BUILDS-85 The reason it worked for me, when I tagged RC1, was because I also pointed my maven to use JDK7. So we have couple options here: #1) (Easy)

Re: mesos-slave crashing with CHECK_SOME

That's one of those areas for discussions that is so likely to generate a flame war that I'm hesitant to wade in :) In general, I would agree with the sentiment expressed there: > If the task fails, that is unfortunate, but not the end of the world. Other tasks should not be affected. which is,

Re: Prepping for next release

Uhm, that's a tricky one... Considering that JDK6 was EOL'd in 2011[0] and even JDK7 is now officially out of support from Oracle, I don't think this should be a major issue? I'm also assuming that, if anyone really needs to use JDK6 they can build from source, by simply running `mvn package` and

[VOTE] Release Apache Mesos 0.24.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.24.0. 0.24.0 includes the following: Experimental support for v1 scheduler HTTP API! This release also wraps up support for fetcher.

Re: minimum requirements for hdfs on mesos

We recommend a minimum of 4 nodes with 4 CPU shares and 8GB of RAM available for the default settings. You can lower the settings by adjusting the configuration, but if you do so, you will not be able to store as much data. Thanks, Elizabeth On Tue, Sep 1, 2015 at 2:14 PM, Dvorkin-Contractor,

Re: minimum requirements for hdfs on mesos

hdfs/example-conf/mesosphere-dcos/mesos-site.xml has some example values defined. For example: mesos.hdfs.namenode.cpus 0.25 Furthermore you need at least 5 private slaves to satisfy the restrictions on node collocation. In other words particular nodes are not allowed to run on the same

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

One more question. From the Mesos code it doesn’t look like events are being split or combined, so given I have a client that gives me access to the individual chunks, is it safe to assume that each chunk contains exactly one event? Because that would make parsing the events a lot easier for

Re: mesos-master resource offer details

>Well, the log you mentioned above is when the resource offer is accepted and mesos-master then allocates the cpu. Hi, @Haripriya As far as i know, the log I show above is allocator allocate resource and make a offer. And then trigger Master::offer to send offer to frameworks. So the log above is

Re: mesos-master resource offer details

If the offer is rejected by your framework, could you find this log in mesos: ``` xxx Processing DECLINE call for offers xxx ``` On Wed, Sep 2, 2015 at 1:31 PM, haosdent wrote: > >Well, the log you mentioned above is when the resource offer is accepted > and mesos-master

Re: mesos-master resource offer details

Thanks, but is there no way without tweaking the source code of the framework scheduler that I get the details of the resource offer? I don't see anything in my logs. All I can see is mesos-master: Sending 5 offers to framework 20150815- (marathon) at scheduler-50ajaja@pqr I can't find any

Re: Use "docker start" rather than "docker run"?

Alex and Marco, Thanks very much for your really helpful explanations. For better or worse, neither cpp nor Python are my things; Java's the go-to language for me. Cordially, Paul On Sat, Aug 29, 2015 at 5:23 AM, Marco Massenzio wrote: > Hi Paul, > > +1 to what Alex/Tim