Re: [GPU] [Allocation] "Scarce" Resource Allocation

Thanks Du Fan. So you mean that we should have some clear rules in document or somewhere else to tell or guide cluster admin which resources should be classified as scarce resources, right? On Sat, Jun 18, 2016 at 2:38 AM, Du, Fan wrote: > > > On 2016/6/17 7:57, Guangya Liu

Re: Mesos working groups

+1 From: "Wong, Steven" Reply-To: Date: Thursday, June 16, 2016 at 11:36 AM To: "u...@mesos.apache.org" , mesos Subject: RE: Mesos working groups The existence of working groups on external volume

Re: Slack as the canonical chat channel

+1 For Slack On Jun 18, 2016 4:04 AM, "Vinod Kone" wrote: > Looks like people have jumped the gun here before I sent the email :) > > Here is the context. During the community sync we discussed about using > *Slack* or *HipChat* as our official chat channel instead of our

Re: 1.0.0 RC2

We still have 12 issues, including 1 blocker, targeted for 1.0. Dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa So I'll wait until *monday morning PST *to cut RC2, for the blocker to get resolved and any other targeted issues to land. Also note that with RC2 we will create a

Re: Slack as the canonical chat channel

+1 Slack. As Mesos is maturing and more and more features are coming we can better organize the discussion through channels. On Fri, Jun 17, 2016 at 1:04 PM, Vinod Kone wrote: > Looks like people have jumped the gun here before I sent the email :) > > Here is the context.

Re: Slack as the canonical chat channel

Thanks for chiming in Ross. This is for chat only. Decision making is still done via dev and user lists as always. On Fri, Jun 17, 2016 at 4:40 PM, Ross Gardler wrote: > Is this proposal for *chat* only as the subject says? If so then all good, > use whatever you

RE: Slack as the canonical chat channel

Is this proposal for *chat* only as the subject says? If so then all good, use whatever you like. If, however, the goal is to move some community decision making processes to this channel then this is a problematic proposal. I'll go into details if appropriate, but since I am an observer not a

Re: Slack as the canonical chat channel

+1 to Slack On Fri, Jun 17, 2016 at 6:46 PM Michael Park wrote: > +1 for Slack for me as well, but is it possible/feasible? > > On 17 June 2016 at 18:07, tommy xiao wrote: > > > +1 Slack! > > > > 2016-06-18 4:54 GMT+08:00 Vinod Kone : >

Re: Slack as the canonical chat channel

+1 for Slack for me as well, but is it possible/feasible? On 17 June 2016 at 18:07, tommy xiao wrote: > +1 Slack! > > 2016-06-18 4:54 GMT+08:00 Vinod Kone : > > > -benh, jake : so that they don't get spammed by reply-alls :) > > > > On Fri, Jun 17, 2016 at

Re: Slack as the canonical chat channel

+1 Slack! 2016-06-18 4:54 GMT+08:00 Vinod Kone : > -benh, jake : so that they don't get spammed by reply-alls :) > > On Fri, Jun 17, 2016 at 1:50 PM, Kapil Arya wrote: > > > +1 Slack! > > > > On Fri, Jun 17, 2016 at 4:37 PM, Yan Xu

Re: Slack as the canonical chat channel

-benh, jake : so that they don't get spammed by reply-alls :) On Fri, Jun 17, 2016 at 1:50 PM, Kapil Arya wrote: > +1 Slack! > > On Fri, Jun 17, 2016 at 4:37 PM, Yan Xu wrote: > > > +1 Slack. > > > > On Friday, June 17, 2016, José Guilherme Vanz

Re: Slack as the canonical chat channel

+1 Slack! On Fri, Jun 17, 2016 at 4:37 PM, Yan Xu wrote: > +1 Slack. > > On Friday, June 17, 2016, José Guilherme Vanz > wrote: > > > +1 Slack > > > > On Fri, 17 Jun 2016 at 17:05 Joris Van Remoortere > > wrote: > > > > > +1

Re: Slack as the canonical chat channel

+1 Slack. On Friday, June 17, 2016, José Guilherme Vanz wrote: > +1 Slack > > On Fri, 17 Jun 2016 at 17:05 Joris Van Remoortere > wrote: > > > +1 Slack > > > > — > > *Joris Van Remoortere* > > Mesosphere > > > > On Fri, Jun 17, 2016 at 10:04 PM,

Re: mesos/kafka issues (reviving old thread)

No issues here, we've been running two 8 broker clusters for ~a month without incident, and I plan on rolling it out to one of our larger (~40 broker) clusters next week. My experience with it has been really positive so far, it just pretty much worked out of the box. I'm curious what issues

Re: Slack as the canonical chat channel

+1 Slack On Fri, 17 Jun 2016 at 17:05 Joris Van Remoortere wrote: > +1 Slack > > — > *Joris Van Remoortere* > Mesosphere > > On Fri, Jun 17, 2016 at 10:04 PM, Vinod Kone wrote: > > > Looks like people have jumped the gun here before I sent the email

Slack as the canonical chat channel

Looks like people have jumped the gun here before I sent the email :) Here is the context. During the community sync we discussed about using *Slack* or *HipChat* as our official chat channel instead of our current #mesos IRC channel on freenode. The main reasons for using Slack/Hipchat are

Re: Slack as the canonical chat channel

+1 Slack — *Joris Van Remoortere* Mesosphere On Fri, Jun 17, 2016 at 10:04 PM, Vinod Kone wrote: > Looks like people have jumped the gun here before I sent the email :) > > Here is the context. During the community sync we discussed about using > *Slack* or *HipChat* as

Re: mesos/kafka issues (reviving old thread)

​Hi Steve, ​ How long has it been running without problems? I have read on mailing list some people complaining that brokers sometimes disappear etc. Have you come across any such problems? Any other issues that you had to take care of? I tried to use the version you specified and also took the

Re: [GPU] [Allocation] "Scarce" Resource Allocation

On 2016/6/17 7:57, Guangya Liu wrote: @Fan Du, Currently, I think that the scarce resources should be defined by cluster admin, s/he can specify those scarce resources via a flag when master start up. This is not what I mean. IMO, it's not cluster admin's call to decide what resources

Mesos CLI

Hey All, The Mesos CLI is going through a redesign. We are aware that the "mesos-execute" command is used pretty often, so that will be ported into the new CLI. However we're not sure if any of the other current CLI commands are being used at all. The remaining list of commands are as follow: -

Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm - 4pm (Apache Mesos)

+1 Slack. On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo wrote: > +1 Slack! > > /J > > Vaibhav Khanduja wrote on 06/16/2016 22:26:27: > > > From: Vaibhav Khanduja > > To: dev@mesos.apache.org > > Date: 06/16/2016 22:26

Re: Failed to shutdown socket with fd xxx

The shutdown errors are not the issue. The concerning part is this warning: > W0615 15:01:43.285518 4182 linux_launcher.cpp:197] Couldn't find pid > '42322' in 'mesos_executors.slice'. This can lead to lack of proper > resource isolation That indicates a transition from the old systemd lack of

Re: Failed to shutdown socket with fd xxx

Hi, @Qiang. @Joseph have a nice explain about at Shutdown failed on fd http://search-hadoop.com/m/0Vlr6pe7qb2MJX8B1=Re+Benign+Shutdown+failed+on+fd+error+messages Those errors could be ignored. For ``` I0615 15:01:43.324935 4172 mem.cpp:602] Started listening for OOM events for container

Re: Failed to shutdown socket with fd xxx

Can you provide: 1. The version that you are upgrading from. 2. Whether you made any OS / init system changes alongside this upgrade (just to narrow the scope). It is possible that you are upgrading from a version that did not have systemd support to one that does. If so, the upgrade may require

Need shepherd for MESOS-5545 (Rack awareness support for Mesos)

Didn't catch up with today's Community Sync, I guess the saying of "Need shepherd" here almost equates to NULL, but it's still by the courtesy to ask one. :) [Fan / Joris] Rack Awareness * Need to find a shepherd! * AI [Joris]: Ask on the dev@ list for the use case w.r.t frameworks

Failed to shutdown socket with fd xxx

Hi all, I met an issue when upgrading mesos-slave to 0.28.2. At the process of recovering mesos-slave / framework container stage, it produced the following errors. ``` Log file created at: 2016/06/15 15:01:43 Running on machine: mesos-slave-online005-xxx.cloud.xxx.domain Log line format: