Re: Mesos v1 API issues for Go
Hi Vinod, I filed MESOS-5642 for fixing allocator.proto and sent the patch at https://reviews.apache.org/r/48902/. Can you please take a look? Thanks. On Thu, Jun 16, 2016 at 4:19 PM, Vinod Kone wrote: > +dev > > Hey Min, > > Thanks for the report! > > (1) and (3) are already fixed (thanks to @haosdent) and upstreamed. We'll > make sure to fix (2) in 1.0. Do you mind creating an issue and/or sending a > review for (2)? I'll be happy to shepherd. > > > P.S: Don't think your email to dev@ was delivered. Make sure you are > subscribed to it by sending an email to dev-subscr...@mesos.apache.org > > > On Thu, Jun 16, 2016 at 2:53 PM, Zhitao Li wrote: > >> >> -- Forwarded message -- >> From: Min Cai >> Date: Wed, Jun 15, 2016 at 12:12 PM >> Subject: Mesos v1 API issues for Go >> To: dev@mesos.apache.org, zhitaoli...@gmail.com >> >> >> Hey, >> >> We are building a Mesos framework in Go and would like to use the latest >> Mesos v1 API. However, when we emit the Go stubs from Mesos v1 API, we >> encountered a few issues: >> >> (1) A circular package importing from mesos.v1.master to >> mesos.v1.maintenance to mesos.v1.master. >> >> mesos.v1.master (mesos/v1/master.proto) >> ==> mesos.v1.maintenance (mesos/v1/maintenance/maintenance.proto) >> ==> mesos.v1.master (mesos/v1/master/allocator.proto) >> >> (2) We have the same package (mesos.v1.master) with different files in >> different directories (mesos/v1/master.proto and >> mesos/v1/master/allocator.proto) >> >> (3) Go doesn't support multiple packages in a single directory. So we >> need to move agent.proto and master.proto to its own subdirectory. >> >> I was able to get around the issues by moving the proto files in my local >> repro. It would be nice to fix them on the upstream especially for the >> circular package dependency. >> >> (1) mesos/v1/master.proto ==> mesos/v1/master/master.proto >> (2) mesos/v1/master/allocator.proto ==> mesos/v1/allocator/allocator.proto >> (3) mesos/v1/agent.proto ==> mesos/v1/agent/agent.proto >> >> >> Thanks, - Min >> >> >> >> >> -- >> Cheers, >> >> Zhitao Li >> > > -- Cheers, Zhitao Li
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 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 should be > marked as scarce , they can carry out the operation, but should be advised > on based on the clear rule: to what extend the resource is scarce compared > with other resources, and it will affect wDRF by causing starvation for > frameworks which holds scarce resources, that's my point. > > To my best knowledge here, a quantitative study of how wDRF behaves in > scenario of one/multiple scarce resources first will help to verify the > proposed approach, and guide the user of this functionality. > > > > Regarding to the proposal of generic scarce resources, do you have any >> thoughts on this? I can see that giving framework developers the options >> of >> define scarce resources may bring trouble to mesos, it is better to let >> mesos define those scarce but not framework developer. >> >
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 and global resource still makes sense to me From: Jie Yu [mailto:yujie@gmail.com] Sent: Thursday, June 16, 2016 11:00 AM To: mesos; u...@mesos.apache.org Subject: Mesos working groups Hi, I am in the process of formalizing our working groups. We recently moved our working groups wiki to documentation in the repo (Thanks Tomasz!). That'll give us more visibility hopefully. https://github.com/apache/mesos/blob/master/docs/working-groups.md However, I realized that a lot of the working groups listed above are no longer active, or does not make sense anymore. Could you please reply to this thread if you think the working group is still valid. I'll remove the rest. Thanks! - Jie
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 current > #mesos IRC channel on freenode. > > The main reasons for using Slack/Hipchat are > >- In-client chat history >- Discoverability of work group specific channels >- Email notifications when offline >- Modern UX and clients > > During the sync most people preferred the move to *Slack*. I wanted to get > a sense from other community members as well through this email. Please let > us know what you think. > > Note that even if we move to Slack, we will make sure people can still > connect using IRC clients and that the chat history is publicly available > (per ASF guidelines). During the transition period, we might mirror > messages from Slack channel to IRC and vice-versa. > > Thoughts? > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia > wrote: > > > +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 > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm > > > > - 4pm (Apache Mesos) > > > > > > > > + 1 slack > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > > message. > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent wrote: > > > > > > > > > > +1 For Slack. > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > > > wrote: > > > > >> > > > > >> Hello all, > > > > >> Here are the notes from our community sync meeting this afternoon: > > > > >> > > > > >> Attendees: > > > > >> > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > Gilbert, > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > >> > > > > >> Uber: Zhitao Li > > > > >> > > > > >> Agenda/Note: > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing the list of maintainers on > > > > >> http://mesos.apache.org/documentation/latest/committers/ > > > > >> - > > > > >> > > > > >> Add components for > > > > >> - > > > > >> > > > > >> Documentation (docs/*) > > > > >> - > > > > >> > > > > >> Windows (*windows*) > > > > >> - > > > > >> > > > > >> C++ standards (docs/c++-style-guide.md) > > > > >> - > > > > >> > > > > >> HTTP API (http.*) > > > > >> - > > > > >> > > > > >> Persistence > > > > >> - > > > > >> > > > > >> Test infrastructure (src/tests/*) > > > > >> - > > > > >> > > > > >> Build-related > > > > >> - > > > > >> > > > > >>Autotools, CMake > > > > >>- > > > > >> > > > > >> Subdivide Stout > > > > >> - > > > > >> > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > >> - > > > > >> > > > > >> Subdivide Container-related things > > (src/slave/containerizer/*) > > > > >> - > > > > >> > > > > >>Networking > > > > >>- > > > > >> > > > > >>Storage > > > > >>- > > > > >> > > > > >> Resource allocation/Scheduler > > > > >> - > > > > >> > > > > >> Development tools > > > > >> - > > > > >> > > > > >> Think about some tooling to facilitate this > > > > >> - > > > > >> > > > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > > > >> - > > > > >> > > > > >> AI: Ben Mahler will send out an email to the mailing list > about > > > > >> maintainers > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing and updating the roadmap. > > > > >> > > > > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap > > > > >> > > > > >> (NOTE: it’ll be moved to documentation roadmap.md) > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Review of working groups > > > > >> > > > > >> > https://github.com/apache/mesos/blob/master/docs/working-groups.md > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> AI [Jie]: Send emails to working group contacts (Simulation, > > > Performance > > > > >> Isolation, Resource Allocation) > > > > >> - > > > > >> > > > > >> AI [Jie] : Split Nested Container into Pods and Nested > Containers > > > > >> - > > > > >> > > > > >> AI [Jie] : Remove Strategy > > > > >> - > > > > >> > > > > >> AI [Jie]: Send a proposal to dev@ regarding work groups > > > > >> - > > > > >> > > > > >> AI [Kevin] : Add a WG for Community (reviews, maintainers, etc) > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> [Fan / Joris] Rack Awareness > > > > >> - > > > > >> > > > > >> Need to find a shepherd! > > > > >> - > > > > >> > >
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 1.0.x branch and update the version on trunk to 1.1.0. Any further fixes for RC2 will be cherry picked on to that branch. On Wed, Jun 15, 2016 at 4:09 PM, Vinod Kone wrote: > There are still 17 un-resolved issues targeted for 1.0. We have only > couple more days left for the RC cut. Whoever is driving & shepherding > these please make sure to land them. > > > > On Mon, Jun 13, 2016 at 1:58 PM, Vinod Kone wrote: > >> Hi folks, >> >> I'm planning to cut 1.0 RC2 later this week (likely friday). So please >> make sure to get any patches targeted for 1.0 (esp. blockers) upstreamed. >> >> The dashboard for the release is here: >> https://issues.apache.org/jira/issues/?filter=12335793 >> >> Thanks, >> Vinod >> > >
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. 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 > >- In-client chat history >- Discoverability of work group specific channels >- Email notifications when offline >- Modern UX and clients > > During the sync most people preferred the move to *Slack*. I wanted to get > a sense from other community members as well through this email. Please let > us know what you think. > > Note that even if we move to Slack, we will make sure people can still > connect using IRC clients and that the chat history is publicly available > (per ASF guidelines). During the transition period, we might mirror > messages from Slack channel to IRC and vice-versa. > > Thoughts? > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia > wrote: > > > +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 > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm > > > > - 4pm (Apache Mesos) > > > > > > > > + 1 slack > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > > message. > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent wrote: > > > > > > > > > > +1 For Slack. > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > > > wrote: > > > > >> > > > > >> Hello all, > > > > >> Here are the notes from our community sync meeting this afternoon: > > > > >> > > > > >> Attendees: > > > > >> > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > Gilbert, > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > >> > > > > >> Uber: Zhitao Li > > > > >> > > > > >> Agenda/Note: > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing the list of maintainers on > > > > >> http://mesos.apache.org/documentation/latest/committers/ > > > > >> - > > > > >> > > > > >> Add components for > > > > >> - > > > > >> > > > > >> Documentation (docs/*) > > > > >> - > > > > >> > > > > >> Windows (*windows*) > > > > >> - > > > > >> > > > > >> C++ standards (docs/c++-style-guide.md) > > > > >> - > > > > >> > > > > >> HTTP API (http.*) > > > > >> - > > > > >> > > > > >> Persistence > > > > >> - > > > > >> > > > > >> Test infrastructure (src/tests/*) > > > > >> - > > > > >> > > > > >> Build-related > > > > >> - > > > > >> > > > > >>Autotools, CMake > > > > >>- > > > > >> > > > > >> Subdivide Stout > > > > >> - > > > > >> > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > >> - > > > > >> > > > > >> Subdivide Container-related things > > (src/slave/containerizer/*) > > > > >> - > > > > >> > > > > >>Networking > > > > >>- > > > > >> > > > > >>Storage > > > > >>- > > > > >> > > > > >> Resource allocation/Scheduler > > > > >> - > > > > >> > > > > >> Development tools > > > > >> - > > > > >> > > > > >> Think about some tooling to facilitate this > > > > >> - > > > > >> > > > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > > > >> - > > > > >> > > > > >> AI: Ben Mahler will send out an email to the mailing list > about > > > > >> maintainers > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing and updating the roadmap. > > > > >> > > > > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap > > > > >> > > > > >> (NOTE: it’ll be moved to documentation roadmap.md) > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Review of working groups > > > > >> > > > > >> > https://github.com/apache/mesos/blob/master/docs/working-groups.md > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> AI [Jie]: Send emails to working group contacts (Simulation, > > > Performance > > > > >> Isolation, Resource Allocation) > > > > >> - > > > > >> > > > > >> AI [Jie] : Split Nested Container into Pods and Nested > Containers > > > > >> - > > > > >> > > > > >> AI [Jie] : Remove Strategy > > > > >> - > > > > >> > > > > >> AI [Jie]: Send a proposal to dev@ regarding work groups > > > > >> - > > > > >> > > > > >> AI [Kevin] : Add a WG for Community (reviews, maintainers, etc) > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> [Fan / Jo
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 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 participant here I'll assume I'm just lacking context (which by the > way is a worrying sign in itself - observers should be able to observe). > > Ross > > > -Original Message- > > From: Vinod Kone [mailto:vinodk...@apache.org] > > Sent: Friday, June 17, 2016 1:04 PM > > To: dev ; Benjamin Hindman > > ; Jake Farrell > > Subject: 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 > > > >- In-client chat history > >- Discoverability of work group specific channels > >- Email notifications when offline > >- Modern UX and clients > > > > During the sync most people preferred the move to *Slack*. I wanted to > get a > > sense from other community members as well through this email. Please let > > us know what you think. > > > > Note that even if we move to Slack, we will make sure people can still > connect > > using IRC clients and that the chat history is publicly available (per > ASF > > guidelines). During the transition period, we might mirror messages from > > Slack channel to IRC and vice-versa. > > > > Thoughts? > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia > > wrote: > > > > > +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 > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 > > > > > 3pm > > > > > - 4pm (Apache Mesos) > > > > > > > > > > + 1 slack > > > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > > > message. > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent > wrote: > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > > > > wrote: > > > > > >> > > > > > >> Hello all, > > > > > >> Here are the notes from our community sync meeting this > afternoon: > > > > > >> > > > > > >> Attendees: > > > > > >> > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > > Gilbert, > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > >> > > > > > >> Uber: Zhitao Li > > > > > >> > > > > > >> Agenda/Note: > > > > > >> > > > > > >> - > > > > > >> > > > > > >> Reviewing the list of maintainers on > > > > > >> > > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fmesos.ap > > ache.org%2fdocumentation%2flatest%2fcommitters%2f&data=01%7c01%7cR > > oss.Gardler%40microsoft.com%7c4ac63e1133dd404c211008d396ea9ea9%7c > > 72f988bf86f141af91ab2d7cd011db47%7c1&sdata=AJnSyfPVHItaEZaptx0etSg > > h0yGPq8BIyehhGiOLqqg%3d > > > > > >> - > > > > > >> > > > > > >> Add components for > > > > > >> - > > > > > >> > > > > > >> Documentation (docs/*) > > > > > >> - > > > > > >> > > > > > >> Windows (*windows*) > > > > > >> - > > > > > >> > > > > > >> C++ standards (docs/c++-style-guide.md) > > > > > >> - > > > > > >> > > > > > >> HTTP API (http.*) > > > > > >> - > > > > > >> > > > > > >> Persistence > > > > > >> - > > > > > >> > > > > > >> Test infrastructure (src/tests/*) > > > > > >> - > > > > > >> > > > > > >> Build-related > > > > > >> - > > > > > >> > > > > > >>Autotools, CMake > > > > > >>- > > > > > >> > > > > > >> Subdivide Stout > > > > > >> - > > > > > >> > > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > > >> - > > > > > >> > > > > > >> Subdivide Container-related things > > > (src/slave/containerizer/*) > > > > > >> - > > > > > >> > > > > > >>Networking > > > > > >>- > > > > > >> > > > > > >>Storage > > > > > >>- > > > > > >> > > > > > >> Resource allocation/Scheduler > > > > > >> - > > > > > >> > > > > > >> Development tools > > > > > >> - > > > > > >> > > > > > >> Think about some tooling to facilitate this > > > > > >> - > > > > > >> > > > > > >> > > > https://na01.safelinks.protection.outlook.com/?url=http
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 participant here I'll assume I'm just lacking context (which by the way is a worrying sign in itself - observers should be able to observe). Ross > -Original Message- > From: Vinod Kone [mailto:vinodk...@apache.org] > Sent: Friday, June 17, 2016 1:04 PM > To: dev ; Benjamin Hindman > ; Jake Farrell > Subject: 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 > >- In-client chat history >- Discoverability of work group specific channels >- Email notifications when offline >- Modern UX and clients > > During the sync most people preferred the move to *Slack*. I wanted to get a > sense from other community members as well through this email. Please let > us know what you think. > > Note that even if we move to Slack, we will make sure people can still connect > using IRC clients and that the chat history is publicly available (per ASF > guidelines). During the transition period, we might mirror messages from > Slack channel to IRC and vice-versa. > > Thoughts? > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia > wrote: > > > +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 > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 > > > > 3pm > > > > - 4pm (Apache Mesos) > > > > > > > > + 1 slack > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > > message. > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent wrote: > > > > > > > > > > +1 For Slack. > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > > > wrote: > > > > >> > > > > >> Hello all, > > > > >> Here are the notes from our community sync meeting this afternoon: > > > > >> > > > > >> Attendees: > > > > >> > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > Gilbert, > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > >> > > > > >> Uber: Zhitao Li > > > > >> > > > > >> Agenda/Note: > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing the list of maintainers on > > > > >> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fmesos.ap > ache.org%2fdocumentation%2flatest%2fcommitters%2f&data=01%7c01%7cR > oss.Gardler%40microsoft.com%7c4ac63e1133dd404c211008d396ea9ea9%7c > 72f988bf86f141af91ab2d7cd011db47%7c1&sdata=AJnSyfPVHItaEZaptx0etSg > h0yGPq8BIyehhGiOLqqg%3d > > > > >> - > > > > >> > > > > >> Add components for > > > > >> - > > > > >> > > > > >> Documentation (docs/*) > > > > >> - > > > > >> > > > > >> Windows (*windows*) > > > > >> - > > > > >> > > > > >> C++ standards (docs/c++-style-guide.md) > > > > >> - > > > > >> > > > > >> HTTP API (http.*) > > > > >> - > > > > >> > > > > >> Persistence > > > > >> - > > > > >> > > > > >> Test infrastructure (src/tests/*) > > > > >> - > > > > >> > > > > >> Build-related > > > > >> - > > > > >> > > > > >>Autotools, CMake > > > > >>- > > > > >> > > > > >> Subdivide Stout > > > > >> - > > > > >> > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > >> - > > > > >> > > > > >> Subdivide Container-related things > > (src/slave/containerizer/*) > > > > >> - > > > > >> > > > > >>Networking > > > > >>- > > > > >> > > > > >>Storage > > > > >>- > > > > >> > > > > >> Resource allocation/Scheduler > > > > >> - > > > > >> > > > > >> Development tools > > > > >> - > > > > >> > > > > >> Think about some tooling to facilitate this > > > > >> - > > > > >> > > > > >> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flxr.free- > electrons.com%2fsource%2fMAINTAINERS&data=01%7c01%7cRoss.Gardler% > 40microsoft.com%7c4ac63e1133dd404c211008d396ea9ea9%7c72f988bf86f > 141af91ab2d7cd011db47%7c1&sdata=5sEALPw36vWR4VKGcmqqft9nACXj7O > kr%2fq6%2bOhI5LCo%3d > > > > >> - > > > > >> > > > > >> AI: Ben Mahler will send out an email to the mailing list about > > > > >> maintainers > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing and upd
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 : > > > > > -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 < > > guilherme@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > +1 Slack > > > > > > > > > > > > On Fri, 17 Jun 2016 at 17:05 Joris Van Remoortere < > > > jo...@mesosphere.io > > > > > > > > > > > wrote: > > > > > > > > > > > > > +1 Slack > > > > > > > > > > > > > > — > > > > > > > *Joris Van Remoortere* > > > > > > > Mesosphere > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 10:04 PM, Vinod Kone < > > vinodk...@apache.org > > > > > > > > > > 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 > > > > > > current > > > > > > > > #mesos IRC channel on freenode. > > > > > > > > > > > > > > > > The main reasons for using Slack/Hipchat are > > > > > > > > > > > > > > > >- In-client chat history > > > > > > > >- Discoverability of work group specific channels > > > > > > > >- Email notifications when offline > > > > > > > >- Modern UX and clients > > > > > > > > > > > > > > > > During the sync most people preferred the move to *Slack*. I > > > wanted > > > > > to > > > > > > > get > > > > > > > > a sense from other community members as well through this > > email. > > > > > Please > > > > > > > let > > > > > > > > us know what you think. > > > > > > > > > > > > > > > > Note that even if we move to Slack, we will make sure people > > can > > > > > still > > > > > > > > connect using IRC clients and that the chat history is > publicly > > > > > > available > > > > > > > > (per ASF guidelines). During the transition period, we might > > > mirror > > > > > > > > messages from Slack channel to IRC and vice-versa. > > > > > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia < > > > > > vinitmahe...@gmail.com > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > +1 Slack. > > > > > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo < > > > > > guojian...@cn.ibm.com> > > > > > > > > > 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 > > > > > > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun > > 16, > > > > 2016 > > > > > > 3pm > > > > > > > > > > > - 4pm (Apache Mesos) > > > > > > > > > > > > > > > > > > > > > > + 1 slack > > > > > > > > > > > > > > > > > > > > > > Sent from my iPhone. Please excuse for typos and > brevity > > of > > > > > this > > > > > > > > > message. > > > > > > > > > > > > > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent < > > > haosd...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > > > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann < > > > > > > g...@mesosphere.io> > > > > > > > > > > wrote: > > > > > > > > > > > >> > > > > > > > > > > > >> Hello all, > > > > > > > > > > > >> Here are the notes from our community sync meeting > > this > > > > > > > afternoon: > > > > > > > > > > > >> > > > > > > > > > > > >> Attendees: > > > > > > > > > > > >> > > > > > > > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, > Kapil, > > > > Anand, > > > > > > > > > Gilbert, > > > > > > > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > > > > > > > >> > > > > > > > > > > > >> Uber: Zhitao Li > > > > > > > > > > > >> > > > > > > > > > > > >> Agenda/Note: > > > > > > > > > > > >> > > > > > > > > > > > >> - > > > > > > > > > > > >> > > > > > > > > > > > >> Reviewing the list of maintainers on > > > > > > > > > > > >> > > > > http://mesos.apache.org/documentation/latest/committers/ > > > > > > > > > > > >> - > > > > > > > > > > > >> > > > > > > > > > > > >> Add components for > > > > > > > > > > > >> - > > > > > > > > > > > >> > > > > > > > > > > > >> Documentation (docs/*) > > > > > > > > > > > >> - > > > > > > > > > > > >> > > > > > > > > > > > >> Windows (*windows*) > > > > > > > >
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 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 < > guilherme@gmail.com > > > > > > > wrote: > > > > > > > > > +1 Slack > > > > > > > > > > On Fri, 17 Jun 2016 at 17:05 Joris Van Remoortere < > > jo...@mesosphere.io > > > > > > > > > wrote: > > > > > > > > > > > +1 Slack > > > > > > > > > > > > — > > > > > > *Joris Van Remoortere* > > > > > > Mesosphere > > > > > > > > > > > > On Fri, Jun 17, 2016 at 10:04 PM, Vinod Kone < > vinodk...@apache.org > > > > > > > > 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 > > > > > current > > > > > > > #mesos IRC channel on freenode. > > > > > > > > > > > > > > The main reasons for using Slack/Hipchat are > > > > > > > > > > > > > >- In-client chat history > > > > > > >- Discoverability of work group specific channels > > > > > > >- Email notifications when offline > > > > > > >- Modern UX and clients > > > > > > > > > > > > > > During the sync most people preferred the move to *Slack*. I > > wanted > > > > to > > > > > > get > > > > > > > a sense from other community members as well through this > email. > > > > Please > > > > > > let > > > > > > > us know what you think. > > > > > > > > > > > > > > Note that even if we move to Slack, we will make sure people > can > > > > still > > > > > > > connect using IRC clients and that the chat history is publicly > > > > > available > > > > > > > (per ASF guidelines). During the transition period, we might > > mirror > > > > > > > messages from Slack channel to IRC and vice-versa. > > > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia < > > > > vinitmahe...@gmail.com > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > +1 Slack. > > > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo < > > > > guojian...@cn.ibm.com> > > > > > > > > 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 > > > > > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun > 16, > > > 2016 > > > > > 3pm > > > > > > > > > > - 4pm (Apache Mesos) > > > > > > > > > > > > > > > > > > > > + 1 slack > > > > > > > > > > > > > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity > of > > > > this > > > > > > > > message. > > > > > > > > > > > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent < > > haosd...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann < > > > > > g...@mesosphere.io> > > > > > > > > > wrote: > > > > > > > > > > >> > > > > > > > > > > >> Hello all, > > > > > > > > > > >> Here are the notes from our community sync meeting > this > > > > > > afternoon: > > > > > > > > > > >> > > > > > > > > > > >> Attendees: > > > > > > > > > > >> > > > > > > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, > > > Anand, > > > > > > > > Gilbert, > > > > > > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > > > > > > >> > > > > > > > > > > >> Uber: Zhitao Li > > > > > > > > > > >> > > > > > > > > > > >> Agenda/Note: > > > > > > > > > > >> > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > > > > > >> Reviewing the list of maintainers on > > > > > > > > > > >> > > > http://mesos.apache.org/documentation/latest/committers/ > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > > > > > >> Add components for > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > > > > > >> Documentation (docs/*) > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > > > > > >> Windows (*windows*) > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > > > > > >> C++ standards (docs/c++-style-guide.md) > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > > > > > >> HTTP API (http.*) > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > > > > > >> Persistence > > > > > > > > > > >> - > > > > > > > > > > >> > > > > > > >
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 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 < > jo...@mesosphere.io > > > > > > > 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 > > :) > > > > > > > > > > > > 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 > > > > > > > > > > > >- In-client chat history > > > > > >- Discoverability of work group specific channels > > > > > >- Email notifications when offline > > > > > >- Modern UX and clients > > > > > > > > > > > > During the sync most people preferred the move to *Slack*. I > wanted > > > to > > > > > get > > > > > > a sense from other community members as well through this email. > > > Please > > > > > let > > > > > > us know what you think. > > > > > > > > > > > > Note that even if we move to Slack, we will make sure people can > > > still > > > > > > connect using IRC clients and that the chat history is publicly > > > > available > > > > > > (per ASF guidelines). During the transition period, we might > mirror > > > > > > messages from Slack channel to IRC and vice-versa. > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia < > > > vinitmahe...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > +1 Slack. > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo < > > > guojian...@cn.ibm.com> > > > > > > > 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 > > > > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, > > 2016 > > > > 3pm > > > > > > > > > - 4pm (Apache Mesos) > > > > > > > > > > > > > > > > > > + 1 slack > > > > > > > > > > > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of > > > this > > > > > > > message. > > > > > > > > > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent < > haosd...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann < > > > > g...@mesosphere.io> > > > > > > > > wrote: > > > > > > > > > >> > > > > > > > > > >> Hello all, > > > > > > > > > >> Here are the notes from our community sync meeting this > > > > > afternoon: > > > > > > > > > >> > > > > > > > > > >> Attendees: > > > > > > > > > >> > > > > > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, > > Anand, > > > > > > > Gilbert, > > > > > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > > > > > >> > > > > > > > > > >> Uber: Zhitao Li > > > > > > > > > >> > > > > > > > > > >> Agenda/Note: > > > > > > > > > >> > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Reviewing the list of maintainers on > > > > > > > > > >> > > http://mesos.apache.org/documentation/latest/committers/ > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Add components for > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Documentation (docs/*) > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Windows (*windows*) > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> C++ standards (docs/c++-style-guide.md) > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> HTTP API (http.*) > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Persistence > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Test infrastructure (src/tests/*) > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Build-related > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >>Autotools, CMake > > > > > > > > > >>- > > > > > > > > > >> > > > > > > > > > >> Subdivide Stout > > > > > > > > > >> - > > > > > > > > > >> > > > > > > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > >
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 > > 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, 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 > > > current > > > > > #mesos IRC channel on freenode. > > > > > > > > > > The main reasons for using Slack/Hipchat are > > > > > > > > > >- In-client chat history > > > > >- Discoverability of work group specific channels > > > > >- Email notifications when offline > > > > >- Modern UX and clients > > > > > > > > > > During the sync most people preferred the move to *Slack*. I wanted > > to > > > > get > > > > > a sense from other community members as well through this email. > > Please > > > > let > > > > > us know what you think. > > > > > > > > > > Note that even if we move to Slack, we will make sure people can > > still > > > > > connect using IRC clients and that the chat history is publicly > > > available > > > > > (per ASF guidelines). During the transition period, we might mirror > > > > > messages from Slack channel to IRC and vice-versa. > > > > > > > > > > Thoughts? > > > > > > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia < > > vinitmahe...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > +1 Slack. > > > > > > > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo < > > guojian...@cn.ibm.com> > > > > > > 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 > > > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, > 2016 > > > 3pm > > > > > > > > - 4pm (Apache Mesos) > > > > > > > > > > > > > > > > + 1 slack > > > > > > > > > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of > > this > > > > > > message. > > > > > > > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent > > > > wrote: > > > > > > > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann < > > > g...@mesosphere.io> > > > > > > > wrote: > > > > > > > > >> > > > > > > > > >> Hello all, > > > > > > > > >> Here are the notes from our community sync meeting this > > > > afternoon: > > > > > > > > >> > > > > > > > > >> Attendees: > > > > > > > > >> > > > > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, > Anand, > > > > > > Gilbert, > > > > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > > > > >> > > > > > > > > >> Uber: Zhitao Li > > > > > > > > >> > > > > > > > > >> Agenda/Note: > > > > > > > > >> > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Reviewing the list of maintainers on > > > > > > > > >> > http://mesos.apache.org/documentation/latest/committers/ > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Add components for > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Documentation (docs/*) > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Windows (*windows*) > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> C++ standards (docs/c++-style-guide.md) > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> HTTP API (http.*) > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Persistence > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Test infrastructure (src/tests/*) > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Build-related > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >>Autotools, CMake > > > > > > > > >>- > > > > > > > > >> > > > > > > > > >> Subdivide Stout > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >> Subdivide Container-related things > > > > > > (src/slave/containerizer/*) > > > > > > > > >> - > > > > > > > > >> > > > > > > > > >>Networking > > > > > > > > >>- > > > > > > > > >> > > > > > > > > >>Storage > > > > > > > > >>- > > > > > > > > >> > > > > > > > > >> Resource allocation/Sc
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 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 our official chat channel instead of our > > current > > > > #mesos IRC channel on freenode. > > > > > > > > The main reasons for using Slack/Hipchat are > > > > > > > >- In-client chat history > > > >- Discoverability of work group specific channels > > > >- Email notifications when offline > > > >- Modern UX and clients > > > > > > > > During the sync most people preferred the move to *Slack*. I wanted > to > > > get > > > > a sense from other community members as well through this email. > Please > > > let > > > > us know what you think. > > > > > > > > Note that even if we move to Slack, we will make sure people can > still > > > > connect using IRC clients and that the chat history is publicly > > available > > > > (per ASF guidelines). During the transition period, we might mirror > > > > messages from Slack channel to IRC and vice-versa. > > > > > > > > Thoughts? > > > > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia < > vinitmahe...@gmail.com > > > > > > > wrote: > > > > > > > > > +1 Slack. > > > > > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo < > guojian...@cn.ibm.com> > > > > > 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 > > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 > > 3pm > > > > > > > - 4pm (Apache Mesos) > > > > > > > > > > > > > > + 1 slack > > > > > > > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of > this > > > > > message. > > > > > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent > > > wrote: > > > > > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann < > > g...@mesosphere.io> > > > > > > wrote: > > > > > > > >> > > > > > > > >> Hello all, > > > > > > > >> Here are the notes from our community sync meeting this > > > afternoon: > > > > > > > >> > > > > > > > >> Attendees: > > > > > > > >> > > > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > > > > Gilbert, > > > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > > > >> > > > > > > > >> Uber: Zhitao Li > > > > > > > >> > > > > > > > >> Agenda/Note: > > > > > > > >> > > > > > > > >> - > > > > > > > >> > > > > > > > >> Reviewing the list of maintainers on > > > > > > > >> http://mesos.apache.org/documentation/latest/committers/ > > > > > > > >> - > > > > > > > >> > > > > > > > >> Add components for > > > > > > > >> - > > > > > > > >> > > > > > > > >> Documentation (docs/*) > > > > > > > >> - > > > > > > > >> > > > > > > > >> Windows (*windows*) > > > > > > > >> - > > > > > > > >> > > > > > > > >> C++ standards (docs/c++-style-guide.md) > > > > > > > >> - > > > > > > > >> > > > > > > > >> HTTP API (http.*) > > > > > > > >> - > > > > > > > >> > > > > > > > >> Persistence > > > > > > > >> - > > > > > > > >> > > > > > > > >> Test infrastructure (src/tests/*) > > > > > > > >> - > > > > > > > >> > > > > > > > >> Build-related > > > > > > > >> - > > > > > > > >> > > > > > > > >>Autotools, CMake > > > > > > > >>- > > > > > > > >> > > > > > > > >> Subdivide Stout > > > > > > > >> - > > > > > > > >> > > > > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > > > > >> - > > > > > > > >> > > > > > > > >> Subdivide Container-related things > > > > > (src/slave/containerizer/*) > > > > > > > >> - > > > > > > > >> > > > > > > > >>Networking > > > > > > > >>- > > > > > > > >> > > > > > > > >>Storage > > > > > > > >>- > > > > > > > >> > > > > > > > >> Resource allocation/Scheduler > > > > > > > >> - > > > > > > > >> > > > > > > > >> Development tools > > > > > > > >> - > > > > > > > >> > > > > > > > >> Think about some tooling to facilitate this > > > > > > > >> - > > > > > > > >> > > > > > > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > > > > > > >> - > > > > > > > >> > > > > > > > >> AI: Ben Mahler will send out an email to the mailing > l
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, 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 > current > > > #mesos IRC channel on freenode. > > > > > > The main reasons for using Slack/Hipchat are > > > > > >- In-client chat history > > >- Discoverability of work group specific channels > > >- Email notifications when offline > > >- Modern UX and clients > > > > > > During the sync most people preferred the move to *Slack*. I wanted to > > get > > > a sense from other community members as well through this email. Please > > let > > > us know what you think. > > > > > > Note that even if we move to Slack, we will make sure people can still > > > connect using IRC clients and that the chat history is publicly > available > > > (per ASF guidelines). During the transition period, we might mirror > > > messages from Slack channel to IRC and vice-versa. > > > > > > Thoughts? > > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia > > > > wrote: > > > > > > > +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 > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 > 3pm > > > > > > - 4pm (Apache Mesos) > > > > > > > > > > > > + 1 slack > > > > > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > > > > message. > > > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent > > wrote: > > > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann < > g...@mesosphere.io> > > > > > wrote: > > > > > > >> > > > > > > >> Hello all, > > > > > > >> Here are the notes from our community sync meeting this > > afternoon: > > > > > > >> > > > > > > >> Attendees: > > > > > > >> > > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > > > Gilbert, > > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > > >> > > > > > > >> Uber: Zhitao Li > > > > > > >> > > > > > > >> Agenda/Note: > > > > > > >> > > > > > > >> - > > > > > > >> > > > > > > >> Reviewing the list of maintainers on > > > > > > >> http://mesos.apache.org/documentation/latest/committers/ > > > > > > >> - > > > > > > >> > > > > > > >> Add components for > > > > > > >> - > > > > > > >> > > > > > > >> Documentation (docs/*) > > > > > > >> - > > > > > > >> > > > > > > >> Windows (*windows*) > > > > > > >> - > > > > > > >> > > > > > > >> C++ standards (docs/c++-style-guide.md) > > > > > > >> - > > > > > > >> > > > > > > >> HTTP API (http.*) > > > > > > >> - > > > > > > >> > > > > > > >> Persistence > > > > > > >> - > > > > > > >> > > > > > > >> Test infrastructure (src/tests/*) > > > > > > >> - > > > > > > >> > > > > > > >> Build-related > > > > > > >> - > > > > > > >> > > > > > > >>Autotools, CMake > > > > > > >>- > > > > > > >> > > > > > > >> Subdivide Stout > > > > > > >> - > > > > > > >> > > > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > > > >> - > > > > > > >> > > > > > > >> Subdivide Container-related things > > > > (src/slave/containerizer/*) > > > > > > >> - > > > > > > >> > > > > > > >>Networking > > > > > > >>- > > > > > > >> > > > > > > >>Storage > > > > > > >>- > > > > > > >> > > > > > > >> Resource allocation/Scheduler > > > > > > >> - > > > > > > >> > > > > > > >> Development tools > > > > > > >> - > > > > > > >> > > > > > > >> Think about some tooling to facilitate this > > > > > > >> - > > > > > > >> > > > > > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > > > > > >> - > > > > > > >> > > > > > > >> AI: Ben Mahler will send out an email to the mailing list > > > about > > > > > > >> maintainers > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> - > > > > > > >> > > > > > > >> Reviewing and updating the roadmap. > > > > > > >> > > > > > > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap > > > > > > >> > > > > > > >> (NOTE: it’ll be moved to documentation roadmap.md) > > > > > > >> > > > > > > >> > > > > > > >> - > > > > > > >> > > > > > > >> Review of work
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 you ran into, happy to try to help if you want! On Fri, Jun 17, 2016 at 3:31 PM, Vinit Mahedia wrote: > 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 latest release > of kafka without luck although I am happy to have found someone for whom > it's working. > > > On Fri, Jun 10, 2016 at 3:57 PM, Steve Niemitz > wrote: > > > Just to chime in, I've been running the 0.9.5.1 scheduler as a task on > > another slave without issues. (Aurora runs the kafka-mesos scheduler in > my > > case). > > > > On Thu, Jun 9, 2016 at 2:50 PM, Vinit Mahedia > > wrote: > > > > > Justin, > > > > > > When you say "working" - does it mean kafka-scheduler still has to be > on > > > the same box as mesos-master? or you > > > have it working without that constraint? > > > > > > On Wed, Jun 8, 2016 at 6:07 PM, Justin Ryan > > wrote: > > > > > > > inline > > > > > > > > On 6/8/16, 4:06 PM, "Justin Ryan" wrote: > > > > > > > > >FYI, when I updated to the latest kafka-mesos (0.5.1.0) this problem > > > went > > > > away. FWIW, I’m actually using a branch which updates kafka to > > 0.10.0.0 > > > as > > > > well: > > > > > > > > > > > > > Correction: 0.9.5.1 (current git master) > > > > > > > > > PR for kafka 0.10.0.0 (tests still fail, someone else did the bulk > of > > > > porting but didn’t PR it) : https://github.com/mesos/kafka/pull/220 > > > > > ( ./gradlew jar –x test gets a successful build ) > > > > > > > > > > Issue for the problem discussed in this thread: > > > > https://github.com/mesos/kafka/issues/199 > > > > > > > > > >Cheers! > > > > > > > > > > > > > > > > > > > > > > > > > P Please consider the environment before printing this e-mail > > > > > > > > The information in this electronic mail message is the sender's > > > > confidential business and may be legally privileged. It is intended > > > solely > > > > for the addressee(s). Access to this internet electronic mail message > > by > > > > anyone else is unauthorized. If you are not the intended recipient, > any > > > > disclosure, copying, distribution or any action taken or omitted to > be > > > > taken in reliance on it is prohibited and may be unlawful. The sender > > > > believes that this E-mail and any attachments were free of any virus, > > > worm, > > > > Trojan horse, and/or malicious code when sent. This message and its > > > > attachments could have been infected during transmission. By reading > > the > > > > message and opening any attachments, the recipient accepts full > > > > responsibility for taking protective and remedial action about > viruses > > > and > > > > other defects. The sender's employer is not liable for any loss or > > damage > > > > arising in any way. > > > > > > > > > > > > > > > > -- > > > ~Vinit > > > > > > > > > -- > ~Vinit >
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 :) > > > > 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 > > > >- In-client chat history > >- Discoverability of work group specific channels > >- Email notifications when offline > >- Modern UX and clients > > > > During the sync most people preferred the move to *Slack*. I wanted to > get > > a sense from other community members as well through this email. Please > let > > us know what you think. > > > > Note that even if we move to Slack, we will make sure people can still > > connect using IRC clients and that the chat history is publicly available > > (per ASF guidelines). During the transition period, we might mirror > > messages from Slack channel to IRC and vice-versa. > > > > Thoughts? > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia > > wrote: > > > > > +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 > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm > > > > > - 4pm (Apache Mesos) > > > > > > > > > > + 1 slack > > > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > > > message. > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent > wrote: > > > > > > > > > > > > +1 For Slack. > > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > > > > wrote: > > > > > >> > > > > > >> Hello all, > > > > > >> Here are the notes from our community sync meeting this > afternoon: > > > > > >> > > > > > >> Attendees: > > > > > >> > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > > Gilbert, > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > > >> > > > > > >> Uber: Zhitao Li > > > > > >> > > > > > >> Agenda/Note: > > > > > >> > > > > > >> - > > > > > >> > > > > > >> Reviewing the list of maintainers on > > > > > >> http://mesos.apache.org/documentation/latest/committers/ > > > > > >> - > > > > > >> > > > > > >> Add components for > > > > > >> - > > > > > >> > > > > > >> Documentation (docs/*) > > > > > >> - > > > > > >> > > > > > >> Windows (*windows*) > > > > > >> - > > > > > >> > > > > > >> C++ standards (docs/c++-style-guide.md) > > > > > >> - > > > > > >> > > > > > >> HTTP API (http.*) > > > > > >> - > > > > > >> > > > > > >> Persistence > > > > > >> - > > > > > >> > > > > > >> Test infrastructure (src/tests/*) > > > > > >> - > > > > > >> > > > > > >> Build-related > > > > > >> - > > > > > >> > > > > > >>Autotools, CMake > > > > > >>- > > > > > >> > > > > > >> Subdivide Stout > > > > > >> - > > > > > >> > > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > > >> - > > > > > >> > > > > > >> Subdivide Container-related things > > > (src/slave/containerizer/*) > > > > > >> - > > > > > >> > > > > > >>Networking > > > > > >>- > > > > > >> > > > > > >>Storage > > > > > >>- > > > > > >> > > > > > >> Resource allocation/Scheduler > > > > > >> - > > > > > >> > > > > > >> Development tools > > > > > >> - > > > > > >> > > > > > >> Think about some tooling to facilitate this > > > > > >> - > > > > > >> > > > > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > > > > >> - > > > > > >> > > > > > >> AI: Ben Mahler will send out an email to the mailing list > > about > > > > > >> maintainers > > > > > >> > > > > > >> > > > > > >> > > > > > >> - > > > > > >> > > > > > >> Reviewing and updating the roadmap. > > > > > >> > > > > > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap > > > > > >> > > > > > >> (NOTE: it’ll be moved to documentation roadmap.md) > > > > > >> > > > > > >> > > > > > >> - > > > > > >> > > > > > >> Review of working groups > > > > > >> > > > > > >> > > https://github.com/apache/mesos/blob/master/docs/working-groups.md > > > > > >> > > > > > >> > > > > > >> - > > > > > >> > > > > > >> AI [Jie]: Send emails to working group contacts (Simulation, > > > > Performance > > > > > >> Isolation, Resource Allocation) > > > > > >> - > > > > > >> > > > > > >> AI [Jie] : Split Nested Container into Pods and Nested > > Containers > > > >
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 - In-client chat history - Discoverability of work group specific channels - Email notifications when offline - Modern UX and clients During the sync most people preferred the move to *Slack*. I wanted to get a sense from other community members as well through this email. Please let us know what you think. Note that even if we move to Slack, we will make sure people can still connect using IRC clients and that the chat history is publicly available (per ASF guidelines). During the transition period, we might mirror messages from Slack channel to IRC and vice-versa. Thoughts? On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia wrote: > +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 > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm > > > - 4pm (Apache Mesos) > > > > > > + 1 slack > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > message. > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent wrote: > > > > > > > > +1 For Slack. > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > > wrote: > > > >> > > > >> Hello all, > > > >> Here are the notes from our community sync meeting this afternoon: > > > >> > > > >> Attendees: > > > >> > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > Gilbert, > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > >> > > > >> Uber: Zhitao Li > > > >> > > > >> Agenda/Note: > > > >> > > > >> - > > > >> > > > >> Reviewing the list of maintainers on > > > >> http://mesos.apache.org/documentation/latest/committers/ > > > >> - > > > >> > > > >> Add components for > > > >> - > > > >> > > > >> Documentation (docs/*) > > > >> - > > > >> > > > >> Windows (*windows*) > > > >> - > > > >> > > > >> C++ standards (docs/c++-style-guide.md) > > > >> - > > > >> > > > >> HTTP API (http.*) > > > >> - > > > >> > > > >> Persistence > > > >> - > > > >> > > > >> Test infrastructure (src/tests/*) > > > >> - > > > >> > > > >> Build-related > > > >> - > > > >> > > > >>Autotools, CMake > > > >>- > > > >> > > > >> Subdivide Stout > > > >> - > > > >> > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > >> - > > > >> > > > >> Subdivide Container-related things > (src/slave/containerizer/*) > > > >> - > > > >> > > > >>Networking > > > >>- > > > >> > > > >>Storage > > > >>- > > > >> > > > >> Resource allocation/Scheduler > > > >> - > > > >> > > > >> Development tools > > > >> - > > > >> > > > >> Think about some tooling to facilitate this > > > >> - > > > >> > > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > > >> - > > > >> > > > >> AI: Ben Mahler will send out an email to the mailing list about > > > >> maintainers > > > >> > > > >> > > > >> > > > >> - > > > >> > > > >> Reviewing and updating the roadmap. > > > >> > > > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap > > > >> > > > >> (NOTE: it’ll be moved to documentation roadmap.md) > > > >> > > > >> > > > >> - > > > >> > > > >> Review of working groups > > > >> > > > >> https://github.com/apache/mesos/blob/master/docs/working-groups.md > > > >> > > > >> > > > >> - > > > >> > > > >> AI [Jie]: Send emails to working group contacts (Simulation, > > Performance > > > >> Isolation, Resource Allocation) > > > >> - > > > >> > > > >> AI [Jie] : Split Nested Container into Pods and Nested Containers > > > >> - > > > >> > > > >> AI [Jie] : Remove Strategy > > > >> - > > > >> > > > >> AI [Jie]: Send a proposal to dev@ regarding work groups > > > >> - > > > >> > > > >> AI [Kevin] : Add a WG for Community (reviews, maintainers, etc) > > > >> > > > >> > > > >> > > > >> - > > > >> > > > >> [Fan / Joris] Rack Awareness > > > >> - > > > >> > > > >> Need to find a shepherd! > > > >> - > > > >> > > > >> AI [Joris]: Ask on the dev@ list for the use case w.r.t > > frameworks > > > >> > > > >> > > > >> > > > >> - > > > >> > > > >> Closing stale reviews ( > 3 months) > > > >> - > > > >> > > > >> AI [Joris/Artem/Vinod/Joseph]: Policy for re-opening reviews > > > >> - > > > >> > > > >> AI [Joris/Artem] : Email dev@ as a heads up before closing the > > > >> reviews (referencing above
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 our official chat channel instead of our current > #mesos IRC channel on freenode. > > The main reasons for using Slack/Hipchat are > >- In-client chat history >- Discoverability of work group specific channels >- Email notifications when offline >- Modern UX and clients > > During the sync most people preferred the move to *Slack*. I wanted to get > a sense from other community members as well through this email. Please let > us know what you think. > > Note that even if we move to Slack, we will make sure people can still > connect using IRC clients and that the chat history is publicly available > (per ASF guidelines). During the transition period, we might mirror > messages from Slack channel to IRC and vice-versa. > > Thoughts? > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia > wrote: > > > +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 > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm > > > > - 4pm (Apache Mesos) > > > > > > > > + 1 slack > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of this > > message. > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent wrote: > > > > > > > > > > +1 For Slack. > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > > > wrote: > > > > >> > > > > >> Hello all, > > > > >> Here are the notes from our community sync meeting this afternoon: > > > > >> > > > > >> Attendees: > > > > >> > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, > > Gilbert, > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > > > >> > > > > >> Uber: Zhitao Li > > > > >> > > > > >> Agenda/Note: > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing the list of maintainers on > > > > >> http://mesos.apache.org/documentation/latest/committers/ > > > > >> - > > > > >> > > > > >> Add components for > > > > >> - > > > > >> > > > > >> Documentation (docs/*) > > > > >> - > > > > >> > > > > >> Windows (*windows*) > > > > >> - > > > > >> > > > > >> C++ standards (docs/c++-style-guide.md) > > > > >> - > > > > >> > > > > >> HTTP API (http.*) > > > > >> - > > > > >> > > > > >> Persistence > > > > >> - > > > > >> > > > > >> Test infrastructure (src/tests/*) > > > > >> - > > > > >> > > > > >> Build-related > > > > >> - > > > > >> > > > > >>Autotools, CMake > > > > >>- > > > > >> > > > > >> Subdivide Stout > > > > >> - > > > > >> > > > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > > > >> - > > > > >> > > > > >> Subdivide Container-related things > > (src/slave/containerizer/*) > > > > >> - > > > > >> > > > > >>Networking > > > > >>- > > > > >> > > > > >>Storage > > > > >>- > > > > >> > > > > >> Resource allocation/Scheduler > > > > >> - > > > > >> > > > > >> Development tools > > > > >> - > > > > >> > > > > >> Think about some tooling to facilitate this > > > > >> - > > > > >> > > > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > > > >> - > > > > >> > > > > >> AI: Ben Mahler will send out an email to the mailing list > about > > > > >> maintainers > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Reviewing and updating the roadmap. > > > > >> > > > > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap > > > > >> > > > > >> (NOTE: it’ll be moved to documentation roadmap.md) > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Review of working groups > > > > >> > > > > >> > https://github.com/apache/mesos/blob/master/docs/working-groups.md > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> AI [Jie]: Send emails to working group contacts (Simulation, > > > Performance > > > > >> Isolation, Resource Allocation) > > > > >> - > > > > >> > > > > >> AI [Jie] : Split Nested Container into Pods and Nested > Containers > > > > >> - > > > > >> > > > > >> AI [Jie] : Remove Strategy > > > > >> - > > > > >> > > > > >> AI [Jie]: Send a proposal to dev@ regarding work groups > > > > >> - > > > > >> > > > > >> AI [Kevin] : Add a WG for Community (reviews, maintainers, etc) > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> [Fan / Joris] Rack Awareness > > > > >> - > > > > >> > > > > >> Need to find a s
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 latest release of kafka without luck although I am happy to have found someone for whom it's working. On Fri, Jun 10, 2016 at 3:57 PM, Steve Niemitz wrote: > Just to chime in, I've been running the 0.9.5.1 scheduler as a task on > another slave without issues. (Aurora runs the kafka-mesos scheduler in my > case). > > On Thu, Jun 9, 2016 at 2:50 PM, Vinit Mahedia > wrote: > > > Justin, > > > > When you say "working" - does it mean kafka-scheduler still has to be on > > the same box as mesos-master? or you > > have it working without that constraint? > > > > On Wed, Jun 8, 2016 at 6:07 PM, Justin Ryan > wrote: > > > > > inline > > > > > > On 6/8/16, 4:06 PM, "Justin Ryan" wrote: > > > > > > >FYI, when I updated to the latest kafka-mesos (0.5.1.0) this problem > > went > > > away. FWIW, I’m actually using a branch which updates kafka to > 0.10.0.0 > > as > > > well: > > > > > > > > > > Correction: 0.9.5.1 (current git master) > > > > > > > PR for kafka 0.10.0.0 (tests still fail, someone else did the bulk of > > > porting but didn’t PR it) : https://github.com/mesos/kafka/pull/220 > > > > ( ./gradlew jar –x test gets a successful build ) > > > > > > > > Issue for the problem discussed in this thread: > > > https://github.com/mesos/kafka/issues/199 > > > > > > > >Cheers! > > > > > > > > > > > > > > > > > > > P Please consider the environment before printing this e-mail > > > > > > The information in this electronic mail message is the sender's > > > confidential business and may be legally privileged. It is intended > > solely > > > for the addressee(s). Access to this internet electronic mail message > by > > > anyone else is unauthorized. If you are not the intended recipient, any > > > disclosure, copying, distribution or any action taken or omitted to be > > > taken in reliance on it is prohibited and may be unlawful. The sender > > > believes that this E-mail and any attachments were free of any virus, > > worm, > > > Trojan horse, and/or malicious code when sent. This message and its > > > attachments could have been infected during transmission. By reading > the > > > message and opening any attachments, the recipient accepts full > > > responsibility for taking protective and remedial action about viruses > > and > > > other defects. The sender's employer is not liable for any loss or > damage > > > arising in any way. > > > > > > > > > > > -- > > ~Vinit > > > -- ~Vinit
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 should be marked as scarce , they can carry out the operation, but should be advised on based on the clear rule: to what extend the resource is scarce compared with other resources, and it will affect wDRF by causing starvation for frameworks which holds scarce resources, that's my point. To my best knowledge here, a quantitative study of how wDRF behaves in scenario of one/multiple scarce resources first will help to verify the proposed approach, and guide the user of this functionality. Regarding to the proposal of generic scarce resources, do you have any thoughts on this? I can see that giving framework developers the options of define scarce resources may bring trouble to mesos, it is better to let mesos define those scarce but not framework developer.
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: - cat - ps - tail - scp If anyone is still using them, please let us know. *If a command is not being used it may be removed completely without a deprecation notice. * Thanks!
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 > > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm > > - 4pm (Apache Mesos) > > > > + 1 slack > > > > Sent from my iPhone. Please excuse for typos and brevity of this message. > > > > > On Jun 16, 2016, at 6:46 PM, haosdent wrote: > > > > > > +1 For Slack. > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann > wrote: > > >> > > >> Hello all, > > >> Here are the notes from our community sync meeting this afternoon: > > >> > > >> Attendees: > > >> > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, Gilbert, > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark > > >> > > >> Uber: Zhitao Li > > >> > > >> Agenda/Note: > > >> > > >> - > > >> > > >> Reviewing the list of maintainers on > > >> http://mesos.apache.org/documentation/latest/committers/ > > >> - > > >> > > >> Add components for > > >> - > > >> > > >> Documentation (docs/*) > > >> - > > >> > > >> Windows (*windows*) > > >> - > > >> > > >> C++ standards (docs/c++-style-guide.md) > > >> - > > >> > > >> HTTP API (http.*) > > >> - > > >> > > >> Persistence > > >> - > > >> > > >> Test infrastructure (src/tests/*) > > >> - > > >> > > >> Build-related > > >> - > > >> > > >>Autotools, CMake > > >>- > > >> > > >> Subdivide Stout > > >> - > > >> > > >> Subdivide Libprocess (3rdparty/libprocess/*) > > >> - > > >> > > >> Subdivide Container-related things (src/slave/containerizer/*) > > >> - > > >> > > >>Networking > > >>- > > >> > > >>Storage > > >>- > > >> > > >> Resource allocation/Scheduler > > >> - > > >> > > >> Development tools > > >> - > > >> > > >> Think about some tooling to facilitate this > > >> - > > >> > > >> http://lxr.free-electrons.com/source/MAINTAINERS > > >> - > > >> > > >> AI: Ben Mahler will send out an email to the mailing list about > > >> maintainers > > >> > > >> > > >> > > >> - > > >> > > >> Reviewing and updating the roadmap. > > >> > > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap > > >> > > >> (NOTE: it’ll be moved to documentation roadmap.md) > > >> > > >> > > >> - > > >> > > >> Review of working groups > > >> > > >> https://github.com/apache/mesos/blob/master/docs/working-groups.md > > >> > > >> > > >> - > > >> > > >> AI [Jie]: Send emails to working group contacts (Simulation, > Performance > > >> Isolation, Resource Allocation) > > >> - > > >> > > >> AI [Jie] : Split Nested Container into Pods and Nested Containers > > >> - > > >> > > >> AI [Jie] : Remove Strategy > > >> - > > >> > > >> AI [Jie]: Send a proposal to dev@ regarding work groups > > >> - > > >> > > >> AI [Kevin] : Add a WG for Community (reviews, maintainers, etc) > > >> > > >> > > >> > > >> - > > >> > > >> [Fan / Joris] Rack Awareness > > >> - > > >> > > >> Need to find a shepherd! > > >> - > > >> > > >> AI [Joris]: Ask on the dev@ list for the use case w.r.t > frameworks > > >> > > >> > > >> > > >> - > > >> > > >> Closing stale reviews ( > 3 months) > > >> - > > >> > > >> AI [Joris/Artem/Vinod/Joseph]: Policy for re-opening reviews > > >> - > > >> > > >> AI [Joris/Artem] : Email dev@ as a heads up before closing the > > >> reviews (referencing above policy) > > >> - > > >> > > >> AI [Artem] : Revive Community Kanban board to properly prioritize > and > > >> track issues > > >> > > >> > > >> > > >> - > > >> > > >> Community metrics (e.g., affiliations) > > >> - > > >> > > >> AI [Mpark] : Blog post around Mesocon NA community talk > > >> - > > >> > > >> AI [Artem] : Email dev@ and personally to solicit affiliations > for > > >> contributor metrics > > >> > > >> > > >> > > >> - > > >> > > >> Communication Channel > > >> - > > >> > > >> Slack, HipChat, IRC? > > >> - > > >> > > >> AI [Vinod] : Email dev@ and user@ about using Slack as canonical > > >> communication channel > > >> > > >> > > >>> On Wed, Jun 15, 2016 at 6:46 PM, Greg Mann > wrote: > > >>> > > >>> Also note: tomorrow's community sync will be hosted at Mesosphere HQ, > 88 > > >>> Stevenson St., San Francisco, CA. Community members are welcome to > attend > > >>> in person! > > >>> > > >>> As usual, Google Hangout and Youtube links for the meeting will be > posted > > >>> in the Google doc just before the meeting begins. > > >>> > > >>> Cheers, > > >>> Greg > > >>> > > On Wed, Jun 15, 2016 at 3:01 PM, Michael Park > wrote: > > > > -- Forwarded message -
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 support to the new support. — *Joris Van Remoortere* Mesosphere On Fri, Jun 17, 2016 at 2:35 PM, haosdent wrote: > Hi, @Qiang. > > @Joseph have a nice explain about at Shutdown failed on fd > > http://search-hadoop.com/m/0Vlr6pe7qb2MJX8B1&subj=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 f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > ``` > > These are normal info log, it happen when Mesos CgroupMemIsolator register > oom hooks for your containers. > > On Fri, Jun 17, 2016 at 8:22 PM, Joris Van Remoortere > > wrote: > > > 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 > restarting > > the tasks (either by themselves, or just starting a fresh agent). Please > > check out some of the work in MESOS-3007 to get a better understanding of > > what the issue I am referring to is. > > > > If you can verify that you are making one of these transitions from a bad > > world to a good world, then you can devise a plan for your upgrade. > > > > Joris > > > > — > > *Joris Van Remoortere* > > Mesosphere > > > > On Fri, Jun 17, 2016 at 8:28 AM, Qiang Chen wrote: > > > > > 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: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg > > > 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 > > > W0615 15:01:43.286182 4182 linux_launcher.cpp:197] Couldn't find pid > > > '42312' in 'mesos_executors.slice'. This can lead to lack of proper > > > resource isolation > > > W0615 15:01:43.286669 4182 linux_launcher.cpp:197] Couldn't find pid > > > '42309' in 'mesos_executors.slice'. This can lead to lack of proper > > > resource isolation > > > W0615 15:01:43.287144 4182 linux_launcher.cpp:197] Couldn't find pid > > > '42304' in 'mesos_executors.slice'. This can lead to lack of proper > > > resource isolation > > > W0615 15:01:43.287636 4182 linux_launcher.cpp:197] Couldn't find pid > > > '42300' in 'mesos_executors.slice'. This can lead to lack of proper > > > resource isolation > > > W0615 15:01:43.288120 4182 linux_launcher.cpp:197] Couldn't find pid > > > '42317' in 'mesos_executors.slice'. This can lead to lack of proper > > > resource isolation > > > E0615 15:01:43.471676 4201 process.cpp:1958] Failed to shutdown socket > > > with fd 24: Transport endpoint is not connected > > > E0615 15:01:43.476007 4201 process.cpp:1958] Failed to shutdown socket > > > with fd 24: Transport endpoint is not connected > > > E0615 15:01:43.476143 4201 process.cpp:1958] Failed to shutdown socket > > > with fd 24: Transport endpoint is not connected > > > E0615 15:01:43.476272 4201 process.cpp:1958] Failed to shutdown socket > > > with fd 24: Transport endpoint is not connected > > > E0615 15:01:43.476483 4201 process.cpp:1958] Failed to shutdown socket > > > with fd 24: Transport endpoint is not connected > > > E0615 15:01:43.476618 4201 process.cpp:1958] Failed to shutdown socket > > > with fd 24: Transport endpoint is not connected > > > > > > ``` > > > > > > And it will also cause the OOM errors, such as: > > > > > > ``` > > > I0615 15:01:43.324935 4172 mem.cpp:602] Started listening for OOM > events > > > for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > > I0615 15:01:43.325469 4172 mem.cpp:722] Started listening on low memory > > > pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > > I0615 15:01:43.326004 4172 mem.cpp:722] Started listening on medium > > > memory pressure events for container > f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > > I0615 15:01:43.326539 4172 mem.cpp:722] Started listening on critical > > > memory pressure events for container > f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > > > > > ``` > > > > > > Did someone suffer this? thanks. > > > > > > -- > > > Best Regards, > > > Chen, Qiang > > > > > > > > > > > > -- > Best Regards, > Haosdent Huang >
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&subj=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 f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc ``` These are normal info log, it happen when Mesos CgroupMemIsolator register oom hooks for your containers. On Fri, Jun 17, 2016 at 8:22 PM, Joris Van Remoortere wrote: > 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 restarting > the tasks (either by themselves, or just starting a fresh agent). Please > check out some of the work in MESOS-3007 to get a better understanding of > what the issue I am referring to is. > > If you can verify that you are making one of these transitions from a bad > world to a good world, then you can devise a plan for your upgrade. > > Joris > > — > *Joris Van Remoortere* > Mesosphere > > On Fri, Jun 17, 2016 at 8:28 AM, Qiang Chen wrote: > > > 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: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg > > 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 > > W0615 15:01:43.286182 4182 linux_launcher.cpp:197] Couldn't find pid > > '42312' in 'mesos_executors.slice'. This can lead to lack of proper > > resource isolation > > W0615 15:01:43.286669 4182 linux_launcher.cpp:197] Couldn't find pid > > '42309' in 'mesos_executors.slice'. This can lead to lack of proper > > resource isolation > > W0615 15:01:43.287144 4182 linux_launcher.cpp:197] Couldn't find pid > > '42304' in 'mesos_executors.slice'. This can lead to lack of proper > > resource isolation > > W0615 15:01:43.287636 4182 linux_launcher.cpp:197] Couldn't find pid > > '42300' in 'mesos_executors.slice'. This can lead to lack of proper > > resource isolation > > W0615 15:01:43.288120 4182 linux_launcher.cpp:197] Couldn't find pid > > '42317' in 'mesos_executors.slice'. This can lead to lack of proper > > resource isolation > > E0615 15:01:43.471676 4201 process.cpp:1958] Failed to shutdown socket > > with fd 24: Transport endpoint is not connected > > E0615 15:01:43.476007 4201 process.cpp:1958] Failed to shutdown socket > > with fd 24: Transport endpoint is not connected > > E0615 15:01:43.476143 4201 process.cpp:1958] Failed to shutdown socket > > with fd 24: Transport endpoint is not connected > > E0615 15:01:43.476272 4201 process.cpp:1958] Failed to shutdown socket > > with fd 24: Transport endpoint is not connected > > E0615 15:01:43.476483 4201 process.cpp:1958] Failed to shutdown socket > > with fd 24: Transport endpoint is not connected > > E0615 15:01:43.476618 4201 process.cpp:1958] Failed to shutdown socket > > with fd 24: Transport endpoint is not connected > > > > ``` > > > > And it will also cause the OOM errors, such as: > > > > ``` > > I0615 15:01:43.324935 4172 mem.cpp:602] Started listening for OOM events > > for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > I0615 15:01:43.325469 4172 mem.cpp:722] Started listening on low memory > > pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > I0615 15:01:43.326004 4172 mem.cpp:722] Started listening on medium > > memory pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > I0615 15:01:43.326539 4172 mem.cpp:722] Started listening on critical > > memory pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > > > ``` > > > > Did someone suffer this? thanks. > > > > -- > > Best Regards, > > Chen, Qiang > > > > > -- Best Regards, Haosdent Huang
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 restarting the tasks (either by themselves, or just starting a fresh agent). Please check out some of the work in MESOS-3007 to get a better understanding of what the issue I am referring to is. If you can verify that you are making one of these transitions from a bad world to a good world, then you can devise a plan for your upgrade. Joris — *Joris Van Remoortere* Mesosphere On Fri, Jun 17, 2016 at 8:28 AM, Qiang Chen wrote: > 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: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg > 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 > W0615 15:01:43.286182 4182 linux_launcher.cpp:197] Couldn't find pid > '42312' in 'mesos_executors.slice'. This can lead to lack of proper > resource isolation > W0615 15:01:43.286669 4182 linux_launcher.cpp:197] Couldn't find pid > '42309' in 'mesos_executors.slice'. This can lead to lack of proper > resource isolation > W0615 15:01:43.287144 4182 linux_launcher.cpp:197] Couldn't find pid > '42304' in 'mesos_executors.slice'. This can lead to lack of proper > resource isolation > W0615 15:01:43.287636 4182 linux_launcher.cpp:197] Couldn't find pid > '42300' in 'mesos_executors.slice'. This can lead to lack of proper > resource isolation > W0615 15:01:43.288120 4182 linux_launcher.cpp:197] Couldn't find pid > '42317' in 'mesos_executors.slice'. This can lead to lack of proper > resource isolation > E0615 15:01:43.471676 4201 process.cpp:1958] Failed to shutdown socket > with fd 24: Transport endpoint is not connected > E0615 15:01:43.476007 4201 process.cpp:1958] Failed to shutdown socket > with fd 24: Transport endpoint is not connected > E0615 15:01:43.476143 4201 process.cpp:1958] Failed to shutdown socket > with fd 24: Transport endpoint is not connected > E0615 15:01:43.476272 4201 process.cpp:1958] Failed to shutdown socket > with fd 24: Transport endpoint is not connected > E0615 15:01:43.476483 4201 process.cpp:1958] Failed to shutdown socket > with fd 24: Transport endpoint is not connected > E0615 15:01:43.476618 4201 process.cpp:1958] Failed to shutdown socket > with fd 24: Transport endpoint is not connected > > ``` > > And it will also cause the OOM errors, such as: > > ``` > I0615 15:01:43.324935 4172 mem.cpp:602] Started listening for OOM events > for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > I0615 15:01:43.325469 4172 mem.cpp:722] Started listening on low memory > pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > I0615 15:01:43.326004 4172 mem.cpp:722] Started listening on medium > memory pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > I0615 15:01:43.326539 4172 mem.cpp:722] Started listening on critical > memory pressure events for container f50b4c7a-d1d2-4fc8-abb9-5ab549f168dc > > ``` > > Did someone suffer this? thanks. > > -- > Best Regards, > Chen, Qiang > >
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
