Re: [GSoC] Google Summer of Code

Those suggestions look good to me, however I would strongly urge that they get improvements committed in an incremental way over the course of the 3 months rather than building a replacement to try to swap at the end. > The lack of recent contributions is, AFAIK, due to the complexity of Angular

Re: Support deadline for tasks

a few tasks that should be killed after > some timeout. We currently have some logic in our scheduler to kill these > tasks. Would be nice to delegate this to the executor. > > - Sagar > > On Fri, Mar 23, 2018 at 3:29 PM, Benjamin Mahler <bmah...@apache.org> > wrote: >

Re: API review: max_duration on TaskInfo

In the interest of doing our due diligence, have you studied any prior art? For example, I was surprised to notice that htcondor doesn't really provide this as a first class thing: https://lists.cs.wisc.edu/archive/htcondor-users/2006- November/msg00024.shtml I didn't see it in any other systems

Re: Support deadline for tasks

Sagar, could you share your use case? Or is it exactly the same as Zhitao's? On Fri, Mar 23, 2018 at 3:15 PM, Sagar Sadashiv Patwardhan <sag...@yelp.com> wrote: > +1 > > This will be useful for us(Yelp) as well. > > On Fri, Mar 23, 2018 at 1:31 PM, Benjamin Mahler <bma

Re: Support deadline for tasks

Also, it's advantageous for mesos to be aware of a hard deadline when it comes to resource allocation. We know that some resources will free up and can make better decisions when it comes to pre-emption, for example. Currently, mesos doesn't know if a task will run forever or will run to

Performance Working Group Meeting Notes

Attendees: Benjamin Mahler, Chun-Hung Hsiao, Yan Xu, Greg Mann, James Peach, Gilbert Song Notes: - Created performance dashboard to track performance related work, tickets need to be labeled with "performance" to show up, feel free to tag tickets that you want tracked: https://issues.

Re: Question on status update retry in agent

(1) Assuming you're referring to the scheduler's acknowledgement of a status update, the agent will not forward TS2 until TS1 has been acknowledged. So, TS2 will not be acknowledged before TS1 is acknowledged. FWICT, we'll ignore any violation of this ordering and log a warning. (2) To reverse

Re: API Review: Resize (persistent) volume support

> 3) target volume in `Resource` format: this may not be possible for any CSI volume because the implementation could change certain metadata, so we did not take this approach. Can you expand on this? 3 looks like the best approach since it's idempotent and doesn't require that clients compute

Re: API Review: Quota Limits

and exposing information like you're effective guarantee and limits at a given point in time). On Mon, Mar 12, 2018 at 12:43 PM, Benjamin Mahler <bmah...@apache.org> wrote: > Just to clarify up front, it's still a little unclear to me what the > semantics of 'force' should be.

Re: Welcome Zhitao Li as Mesos Committer and PMC Member

Welcome Zhitao! Thanks for your contributions so far On Mon, Mar 12, 2018 at 2:02 PM, Gilbert Song wrote: > Hi, > > I am excited to announce that the PMC has voted Zhitao Li as a new > committer and member of PMC for the Apache Mesos project. Please join me to > congratulate

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

Welcome Chun! It's been great discussing things with you so far and thanks for the all the hard work! On Sat, Mar 10, 2018 at 9:14 PM, Jie Yu wrote: > Hi, > > I am happy to announce that the PMC has voted Chun-Hung Hsiao as a new > committer and member of PMC for the Apache

Re: API Review: Quota Limits

s? On Mon, Mar 12, 2018 at 1:22 AM, Qian Zhang <zhq527...@gmail.com> wrote: > For the new UPDATE_QUOTA call, do we allow setting limit lower than role's > existing allocation? If yes, does operator have to do it with the 'force' > flag? > > > Regards, > Qian Zhang > &g

API Review: Quota Limits

As discussed during the API working group, we would like to ensure that upcoming API changes are surfaced more broadly than just in Review Board. The hope is that if we surface them on the dev@ list, it will raise awareness and give a chance for more folks to give feedback on things like naming,

Re: Authorization Logging

eviews/comments always welcomed > > Alexander Rojas > alexander.ro...@gmail.com > > > > > On 28. Feb 2018, at 23:52, Benjamin Mahler <bmah...@apache.org> wrote: > > When touching some code, I noticed that authorization logging is currently > done rather inconsistent

Re: Reconsidering `allocatable` check in the allocator

+1 about it not being about network traffic. I the direction we want to head towards is to express and enforce a minimum granularity for scalar resources. For example: CPU: 0.001, if we say that we can only deal with milli-cpus. Disk: 1, if we say that we can only deal with the MB level of disk

Re: Reconsidering `allocatable` check in the allocator

I think (2) would need to be: bool HierarchicalAllocatorProcess::allocatable( const Resources& resources) { if (something outside {cpu, mem, disk} is present) return true else return true iff at least one of {cpu, mem, disk} has >= {MIN_CPU, MIN_MEM, MIN_DISK} } Otherwise, 1 GPU would be

Re: Thoughts on initial implementation to use libarchive?

Having both decompress.hpp and gzip.hpp seems unfortunate, can you look into unifying them? The latter is an existing library that provides the following: -In-memory gzip compression and de-compression

Re: Tasks may be explicitly dropped by agent in Mesos 1.5

Put another way, we currently don't guarantee in-order task delivery to the executor. Due to the changes for MESOS-1720, one special case of task re-ordering now leads to the re-ordered task being dropped (rather than delivered out-of-order as before). Technically, this is strictly better.

Re: Collecting futures in the same actor in libprocess

irst one, > the agent will end up sending `TASK_DROPPED` for the second call. > > If we can have an interface to make sure that `collect()` returns in the > same order > of their dependent futures, this can be avoided. > > On Mar 1, 2018 12:50 PM, "Benjamin Mahler" &l

Re: Collecting futures in the same actor in libprocess

Could you explain the problem in more detail? On Thu, Mar 1, 2018 at 12:15 PM Chun-Hung Hsiao wrote: > Hi all, > > Meng found a bug in `slave.cpp`, where the proper fix requires collecting > futures in order. Currently every `collect` call spawns it's own actor, so > for

Authorization Logging

When touching some code, I noticed that authorization logging is currently done rather inconsistently across the call-sites and many cases do not log the request: $ grep -R -A 3 'LOG.*Authorizing' src Should authorization logging be the concern of an authorizer implementation? For audit purposes

Feb 21 Performance WG Meeting Canceled

Hi folks, since there's nothing on the agenda for this month's meeting. I will cancel it and plan to meet next month. If there are any topics folks would like to discuss let me know and we can schedule one sooner!

Re: http://mesos.apache.org/downloads/ is not up to date

Thanks for pointing this out Adam, I've added mpark who is the release manager for 1.3.2. On Tue, Feb 6, 2018 at 6:12 AM, Adam Cecile wrote: > Hi guys, > > > Did you notice Mesos 1.3.2 is missing from the official download page ? > > http://mesos.apache.org/downloads/ > >

Reminder: Design Doc for Mesos CLI Re-design

I've heard a lot of interest in there being investment in the mesos CLI. For those that are interested, please take a look at the re-design doc and share your feedback: https://docs.google.com/document/d/1r6Iv4Efu8v8IBrcUTjgYkvZ32WVsc gYqrD07OyIglsA/edit Feel free to make comments in the doc,

Re: Looking for shepherd

In case others also look at this thinking this still needs a shepherd, this has been committed. On Mon, Feb 12, 2018 at 6:39 AM, Tomek Janiszewski wrote: > I need someone to review and merge this change > https://reviews.apache.org/r/65569/ > It should fix ARM tests. >

Re: [VOTE] C++14 Upgrade

> I guess we need to test out whether running Mesos built with newer version > of gcc (also glibc) on older version of distro is safe. Is it possible to install the newer gcc / glibc on Jessie? It seems there are some comments on the spreadsheet that say the method posted is not safe? What about

Re: Implicit reconcile "pauses" offer stream in large cluster

Following up, did you gather any perf data for this? On Sat, Dec 30, 2017 at 8:15 AM, Meghdoot bhattacharya < meghdoo...@yahoo.com.invalid> wrote: > Zhitao any further updates on this? > > Thx > > > On Dec 13, 2017, at 1:02 PM, Benjamin Mahler <bmah...@apache.org>

Re: Soliciting Hackathon Ideas

shepherd for that for a while, if there are any > takers I'm happy to rebase against the latest code! > > Tim > > On Wed, Feb 7, 2018 at 11:10 AM James Peach <jor...@gmail.com> wrote: > > > > > > > > On Feb 6, 2018, at 11:21 PM, Benjamin Mahler <bmah...@ap

Re: Soliciting Hackathon Ideas

A couple of ideas from the performance related working group: -Use protobuf arenas for all non-trivial outbound master messages (easy) This can be done piecemeal. -Use move semantics (take a Message&&) in all of the master message handlers to reduce copying (medium) This one can be done

Re: No more Issue update emails

This includes any updates to description, priority, target versions? If I watch a ticket will I still get update emails? On Thu, Feb 1, 2018 at 12:29 PM Vinod Kone wrote: > Hi folks, > > Just a heads up that I've had our JIRA notification scheme changed so that > the

Re: API working group

I'd be interested in participating. Lots to discuss! On Tue, Jan 30, 2018 at 10:42 AM, Vinod Kone wrote: > Hi folks, > > We've had good success with our containerization, performance and community > working groups and so we would like to keep the momentum going and spin up

Re: [Performance] Reminder: Working group meeting tomorrow Jan 17 @ 10 am PST

Thanks Meng for presenting! For those who missed it, notes were added to the agenda: https://docs.google.com/document/d/12hWGuzbqyNWc2l1ysbPcXwc0pzHEy4bodagrlNGCuQU/edit# On Tue, Jan 16, 2018 at 2:00 PM, Benjamin Mahler <bmah...@apache.org> wrote: > On the agenda so far, we'll have

[Performance] Reminder: Working group meeting tomorrow Jan 17 @ 10 am PST

On the agenda so far, we'll have Meng Zhu present some recent benchmark findings that compare the performance of the v0, v1 (protobuf / json) master APIs. There have also been some initial discussions into streaming state into a different actor and/or using a filter language like GraphQL to

Re: Sharing master detector to modules

Just a note that if you increase the number of instances of detectors you wind up increasing the number of instances of our `Zookeeper` client class. This class was written a long time ago and so is still a blocking interface rather than a Future-based non-blocking interface. As a result, the

Re: Replacing ad hoc virtualenvs for testing and linting with tox

+armand, benno, kevin On Fri, Jan 5, 2018 at 12:04 PM, Eric Chung wrote: > Hello mesos devs, > > I'd like to propose that we replace some of our bash scripts for building > ad hoc virtualenvs with tox , a > tool > for automating lifecycle

Re: Mesos 1.5.0 Release

Meng is working on https://issues.apache.org/jira/browse/MESOS-8352 and we should land it tonight if not tomorrow. I can cherry pick if it's after your cut, and worst case it can go in 1.5.1. Have you guys gone over the unresolved items targeted for 1.5.0? I see a lot of stuff, might be good to

Re: empty executor_id field in tasks

The issue that was fixed recently was: https://issues.apache. org/jira/browse/MESOS-8135 This was a bug where we would lose track of executors (and their IDs) in the master for the non-command executor case. I believe it's still the case that command executors are not tracked in the master:

Mesos Blog Posts

Hi folks, I wanted to share with the dev@ list some of the ongoing discussion we've been having in the community working group. One of the things that we're looking to improve is our outward communication in the project. There are many facets to this, but two problems that I'd like to highlight

Re: Reusing `reserve_resources` ACL for static reservation

+alexander, adam On Tue, Dec 12, 2017 at 11:31 AM, Yan Xu wrote: > Hi, > > In https://issues.apache.org/jira/browse/MESOS-8306 I am proposing that we > use an ACL to restrict the roles that agents can statically reserve > resources for to address a security concern in which a

Re: Customize executor_registration_timeout per executor

on, Dec 11, 2017 at 7:37 PM, Benjamin Mahler <bmah...@apache.org> > wrote: > > > On Mon, Dec 11, 2017 at 9:53 AM, James Peach <jor...@gmail.com> wrote: > > > > > > > > > On Dec 11, 2017, at 8:55 AM, Zhitao Li <zhitaoli...@gmail.com> >

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

+1 (binding) make check passes on macOS 10.13.2 with Apple LLVM version 9.0.0 (clang-900.0.39.2) On Thu, Dec 7, 2017 at 2:44 PM, Michael Park wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.3.2. > > The CHANGELOG for the release is

Re: Implicit reconcile "pauses" offer stream in large cluster

You can check the diff, for example: https://github.com/apache/mesos/compare/1.3.0...1.4.0 I didn't notice any changes that look like they would cause this. What do the master logs show during the time frame? Have you profiled what the master and scheduler are doing during this time frame? On

Re: [Performance WG] Reminder: Meeting Dec 13 10am PST

Looks like not enough folks were able to attend, so I canceled this meeting. The notes for this week are in the doc: https://docs.google.com/document/d/12hWGuzbqyNWc2l1ysbPcXwc0pzHEy4bodagrlNGCuQU/edit?usp=sharing On Wed, Dec 13, 2017 at 12:45 AM, Benjamin Mahler <bmah...@apache.org>

[Performance WG] Reminder: Meeting Dec 13 10am PST

Hi folks, just a late reminder that the next performance working group meeting for this week. Please see the Apache Mesos calendar of events for information on how to join. Ben

Re: Customize executor_registration_timeout per executor

On Mon, Dec 11, 2017 at 9:53 AM, James Peach wrote: > > > On Dec 11, 2017, at 8:55 AM, Zhitao Li wrote: > > > > Hi, > > > > We are running tasks which has very large docker images and tasks which > use > > much smaller images in our clusters, Therefore,

Re: Container launch metrics on agent

1) My guess is that we only added the errors because we alerted on there being an error increase. I assume you also care about every error? Having a 'success' count and 'total' count sounds reasonable to me. 2) Not sure, have you read the code? What would you want to be the case? Would you need

Re: mesos git commit: Added a performance working group December 2017 blog post.

he.org/repos/asf/mesos/diff/e7244ae1 > > > > Branch: refs/heads/master > > Commit: e7244ae1eb84a8bfcbe2940107c7f97a53832cf2 > > Parents: 83f81b7 > > Author: Benjamin Mahler <bmah..

Fwd: Request for Participation: The Right Metrics for the Right Project

FYI If anyone is able to look into setting this up that would be great! -- Forwarded message -- From: Daniel Gruno Date: Mon, Nov 27, 2017 at 10:26 AM Subject: Request for Participation: The Right Metrics for the Right Project To: d...@kibble.apache.org Hi

Re: Please use `int_fd` instead of `int` for file descriptors

antics. Do you want these > documented in `stout/os/windows/fd.hpp`? Yes, we have code using int_fd within hashmaps, maps, etc, already across platforms so I assume it has the properties I listed on windows, but it would be good to document that as being something that int_fd is guaranteed to p

Re: Please use `int_fd` instead of `int` for file descriptors

Is it possible to document in that header the properties of int_fd that we can rely on? For example, it has a hash defined for use in unordered map, set, etc. It's a POD type, etc. On Wed, Nov 29, 2017 at 10:17 PM, Andrew Schwartzmeyer < and...@schwartzmeyer.com> wrote: > Hello everyone! > >

Re: Differing DRF flavors over roles and frameworks

On Thu, Nov 30, 2017 at 2:52 PM, Benjamin Bannier < benjamin.bann...@mesosphere.io> wrote: > Hi Ben, > > and thank you for answering. > > > > For frameworks in the same role on the other hand we choose to > normalize > > > with the allocated resources > > > > Within a role, the framework's share

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

+1 (binding) make check on macOS 10.13.1 On Wed, Nov 29, 2017 at 9:17 PM, Adam Bordelon wrote: > +1 (binding) > > Passed all tests in DC/OS integration CI, with a bump to 1.2.x at f8706e5, > just one changelog update before 1.2.3-rc1. >

Re: Differing DRF flavors over roles and frameworks

> For frameworks in the same role on the other hand we choose to normalize with the allocated resources Within a role, the framework's share is evaluated using the *role*'s total allocation as a denominator. Were you referring to the role's total allocation when you said "allocated resources"? I

Re: Welcome Andrew Schwartzmeyer as a new committer and PMC member!

Welcome and thanks for your contributions so far! On Mon, Nov 27, 2017 at 11:00 PM, Joseph Wu wrote: > Hi devs & users, > > I'm happy to announce that Andrew Schwartzmeyer has become a new committer > and member of the PMC for the Apache Mesos project. Please join me in >

Stripping Offer.AllocationInfo and Resource.AllocationInfo for non-MULTI_ROLE schedulers.

Hi folks, When we released MULTI_ROLE support, Offers and Resources within them included additional information, specifically the AllocationInfo which indicated which role was being allocated to: https://github.com/apache/mesos/blob/1.3.0/include/ mesos/v1/mesos.proto#L907-L923

[Performance] Nov 15 Working Group Meeting canceled

Hi folks, the performance working group meeting for November 15th will be canceled and we'll meet next month. Current work is still ongoing from the last meeting: -Dmitry's protobuf upgrade to 3.5.0 for move support. -Dmitry's move support for dispatch/defer and install handlers. This will aim

Re: ClangTidy for Mesos is here!

Thanks Michael and Benjamin! On Sat, Nov 4, 2017 at 3:18 PM, Michael Park wrote: > We've had ClangTidy for Mesos, called MesosTidy for a while checked > into the codebase, but we hadn't actually enabled it on the CI. > > I've created a Mesos-Tidybot job (to accompany

Re: libevent-2.1.8 SSL mode can't trigger recv callback

Yes, Till mentioned to me that we need to adjust our code for 2.1.8: https://issues.apache.org/jira/browse/MESOS-7076 I haven't had time to look into it, would you like to look into what changed and send a patch? On Mon, Nov 6, 2017 at 6:25 AM, Suteng wrote: > Hi, > > We

Re: 1.3.2 Release

Great! I cherry picked Gaston's fix for https://issues.apache.org/ jira/browse/MESOS-8135. On Wed, Nov 1, 2017 at 6:57 PM, Michael Park wrote: > Please reply to this email if you have pending patches to be backported to > 1.3.x, I'm aiming to cut a 1.3.2 on Friday. > >

Re: Sandbox life cycle /age

Hi Venkat, You're seeing that files with a modification time greater than your gc delay of 2 hours are *not* getting deleted? Can you show a full listing of /var/lib/mesos/slave/slaves/? Is there more than 1 entry there? On Fri, Oct 27, 2017 at 8:43 AM, Venkat Morampudi

Re: On the current CI state

Thanks Alex! Also I would like to re-state the importance of everyone subscribing to the builds@ list and helping triage the build failure emails. In particular, if you find a ticket, reply with it so that others don't have to look into it. If there's no ticket, capturing the logs of the bad run

Re: mesos.interface==1.4.0

+kapil Kapil was this missed during the 1.4.0 release? It seems to be in the release guide: http://mesos.apache.org/documentation/latest/release-guide/#updating-external-tooling On Sun, Oct 22, 2017 at 1:38 AM, Erb, Stephan wrote: > Hi, > > the

Re: Build failed in Jenkins: Mesos-Buildbot » autotools,clang,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(ubuntu)&&(!ubuntu-us1)&&(!ubuntu-eu2) #4118

Anyone know what std::system_error with 'Invalid argument' might mean? Or why we're getting a stack trace entirely of '(Unknown)'? I've actually seen the same crash in a scale test cluster, would be great if anyone has any ideas here. On Wed, Aug 16, 2017 at 6:00 PM, Apache Jenkins Server <

Re: [Performance WG] Meeting this Wednesday

this thread or the #performance channel in slack! Ben On Wed, Oct 18, 2017 at 1:41 PM, Judith Malnick <jmaln...@mesosphere.io> wrote: > Hi all, In case you weren't able to make the meeting in person, you can > watch the recording here <https://youtu.be/4XnotRgxuWw>. > > On Mo

Re: Catching the webui up to features

gt; http://u64:5050/metrics/snapshot?jsonp=angular.callbacks._3 > > This is what causes the error modal to pop up on every interval tick of > these AJAX requests. > > Thanks, > Aaron > > On Mon, Sep 25, 2017 at 7:47 PM, Benjamin Mahler <bmah...@apache.org> > wrote: >

[Performance WG] Meeting this Wednesday

Hi folks, We have another performance working group meeting this Wednesday at 10am PST, you can add the calendar here: http://mesos.apache.org/community/ The plan for the meeting is for Yan and Ilya to go over benchmark results for master failover and the HTTP API, respectively. We'll also talk

Design Doc: Hierarchical Quota Guarantees and Limits

Hi folks, As part of the ongoing work for hierarchical role support, Michael Park and I have been working on a design doc that describes how the allocation algorithm needs to be updated to handle hierarchical quota guarantees. Also, as part of this work, we realized it makes sense to also make

Re: [Proposal] Updating levels for verbose logging

perspective, the libprocess info logging usually only for debugging, and the libprocess verbose logging definitely only for debugging. On Mon, Oct 9, 2017 at 3:34 PM, Benjamin Mahler <bmah...@apache.org> wrote: >2. Changing the libprocess verbose logs to start at level 3. Not just

Re: [Proposal] Updating levels for verbose logging

It seems unfortunate to establish an ordering between different component's verbosity levels, how is libprocess to know which level to start at? I suppose you can tell it, but it's not clear that the first level of verbosity in libprocess should come after the max level of verbosity in mesos.

Re: Are there any supported systems without O_CLOEXEC?

Is this altering the minimum Linux or OS X version we support? On Fri, Sep 29, 2017 at 9:15 AM, James Peach wrote: > > > On Sep 27, 2017, at 5:03 PM, James Peach wrote: > > > > Hi all, > > > > In MESOS-8027 and https://reviews.apache.org/r/62638/, I'm

Re: Catching the webui up to features

npoint the exact area > for where the logic is different. Maybe someone that has worked on the UI > in the past can shed more light on this...? > > On Wed, Sep 13, 2017 at 8:03 PM, Benjamin Mahler <bmah...@apache.org> > wrote: > > > +haosdent, vinod > > > > Blamin

Re: [Performance] working group meeting Sept 20 10AM PST

Reminder for those interested. On Tue, Sep 12, 2017 at 5:00 PM Benjamin Mahler <bmah...@apache.org> wrote: > Hi folks, > > It's been awhile since the last peformance working group meeting, so we > wanted to schedule another. The next one is scheduled for Wednesday > Sep

Re: Mesos at Metamarkets

Thanks for sharing this Charles, do you have any feedback (positive or negative) or feature requests for the Mesos project that you want to highlight on the list? On Fri, Sep 15, 2017 at 6:37 PM, Charles Allen < charles.al...@metamarkets.com> wrote: > Just fyi, a post went live that talks a bit

Re: Catching the webui up to features

re groups in > the org upgrade to newer versions of Mesos they will be facing this issue > almost on a daily basis. > > Thanks, > Aaron > > On Mon, Sep 11, 2017 at 2:59 PM, Benjamin Mahler <bmah...@apache.org> > wrote: > > > Hi folks, > > > > Over time

[Performance] working group meeting Sept 20 10AM PST

Hi folks, It's been awhile since the last peformance working group meeting, so we wanted to schedule another. The next one is scheduled for Wednesday September 20 at 10AM PST. Please add items of interest to the agenda:

Catching the webui up to features

Hi folks, Over time the webui has lagged behind for some of the features that have been added. I'm currently tracking what's required to catch it up here: https://issues.apache.org/jira/browse/MESOS-6440 If you know of other features that make sense to display in the webui, feel free to file a

Re: Welcome James Peach as a new committer and PMC memeber!

Thanks for all that you've done so far for the project James! On Wed, Sep 6, 2017 at 2:08 PM, Yan Xu wrote: > Hi Mesos devs and users, > > Please welcome James Peach as a new Apache Mesos committer and PMC member. > > James has been an active contributor to Mesos for over two

Re: [VOTE] Release Apache Mesos 1.4.0 (rc3)

-1 due to https://issues.apache.org/jira/browse/MESOS-7921 Thanks for reporting this Yan, it unfortunately went unnoticed despite CI failures since Aug 3rd. On Mon, Aug 28, 2017 at 12:29 PM, Yan Xu wrote: > Also the libprocess refactor seems to have stability issues: >

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

This will be a big win Benno, thanks for driving it! Nice to see that the heap profiling overhead is really low, I'd love to be able to just hit an endpoint on the master or agent and get a memory profile. I'm a +1 for making it the default, however, I seem to recall hearing that there were some

Re: Moving the website repo from svn to git

Thank you Vinod for driving this! The automatic updates are a huge improvement :) On Wed, Aug 9, 2017 at 1:49 PM, Vinod Kone wrote: > To close the loop on this, the website automation is now live! > > Any changes to the mesos repo will trigger the Mesos-Websitebot CI job

Re: Deprecating `--disable-zlib` in libprocess

Sorry, I think this was me, feel free to remove it from libprocess now that it's required. On Tue, Aug 8, 2017 at 10:57 AM, Chun-Hung Hsiao wrote: > Hi all, > > In libprocess, we have an optional `--disable-zlib` flag, but it's > currently not used > for conditional

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

+1 (binding) ./configure CC=clang CXX=clang++ CXXFLAGS=-Wno-deprecated-declarations --disable-python --disable-java --with-apr=/usr/local/opt/apr/libexec --with-svn=/usr/local/opt/subversion && make check -j8 Ran into a known flaky test: https://issues.apache.org/jira/browse/MESOS-7739 On Tue,

Re: POST vs PUT in v0 HTTP endpoints

feature parity with V1 API)? > > On Tue, Aug 1, 2017 at 3:55 PM, Benjamin Mahler <bmah...@apache.org> > wrote: > > > I noticed that we have some inconsistent usage of POST vs PUT (only 1 > > endpoint uses PUT today), so I did a little survey of our endpoints: > >

POST vs PUT in v0 HTTP endpoints

I noticed that we have some inconsistent usage of POST vs PUT (only 1 endpoint uses PUT today), so I did a little survey of our endpoints: https://docs.google.com/document/d/1yo-ZcKAdrCwBmTDkAKGNLnhK7fAfwatKddZrhtpgyMk/edit?usp=sharing A couple of findings: * We often don't look at the method,

Re: Dropping support for Apple Clang

Can you also tell us a little more about "Apple Clang"? Is it just a wrapper bound to a particular clang version? Why does it exist? Also, do you know what the versioning scheme is? $ clang++ --version Apple LLVM version 8.1.0 (clang-802.0.42) Target: x86_64-apple-darwin16.6.0 Thread model: posix

Re: Mesos Python Daemon Launch

This is generally not something we want users to do (i.e. leak something outside of their container). Mesos will kill all tasks in the cgroup if you're using cgroup isolation, so you would have to ensure the daemon escapes the cgroup. If you're using the posix isolation, you also need to be sure

Re: Performance working group meeting

Thanks to those who joined! Notes were taken in the doc, I'll inline them below for easier consumption. I'll also be looking into getting the video published on the YouTube channel. Notes: -Attendee introductions: Benjamin Hindman, Chun-Hung Hsiao, Benjamin Mahler, Greg Mann, James Peach, Ilya

Re: Performance working group meeting

is the agenda doc, I will update the agenda and the calendar entry with the Zoom details when I have those sorted out: https://docs.google.com/document/d/12hWGuzbqyNWc2l1ysbPcXwc0pzHEy4bodagrlNGCuQU/edit?usp=sharing On Fri, Jul 21, 2017 at 9:03 AM, Benjamin Mahler <bmah...@apache.org> wrote: &

Performance working group meeting

Since there have been several folks working on performance related things lately, I'd like to try to schedule a meeting, this could be recurring if we find it useful, For an agenda, we could discuss: - ongoing work for libprocess optimizations and faster master failovers - existing performance

Re: Mesos Executor fails to launch tasks

Is there anything in the executor logs? On Tue, Jul 18, 2017 at 2:39 PM, Thodoris Zois wrote: > Hello, i am trying to run an executor from jar file. But every time i > launch a task it fails and scheduler terminates `Aborting because task 0 is > in unexpected state

Re: New YouTube channel to house working group recordings?

Added it: https://github.com/apache/mesos/commit/f9a80a0672dc65964aadcafe45051991e94d670a On Mon, Jun 5, 2017 at 8:26 PM, Michael Park <mp...@apache.org> wrote: > Yep. That's the one. > > On Mon, Jun 5, 2017 at 1:48 PM, Benjamin Mahler <bmah...@apache.org> > wrote:

Metrics for committing code for contributors

71 Benjamin Hindman 474 Joris Van Remoortere 617 Benjamin Mahler 1017 Vinod Kone 1022 Jie Yu You can change the date range here if you want to get a more recent snapshot. Note of course that much like the github commit count metrics, this doesn't capture the commits from the svn days where we

Re: RFC: removing process implementations from common headers

Thanks James! As you said, removing Process implementations from the headers is the existing practice, but we need to do a sweep to enforce this consistently. Folks could work on this sweep today to make progress on the 3 benefits you outlined. This proposal to me seems to just be: (1) When

Re: Welcome Greg Mann as a new committer and PMC member!

Thanks for all that you've done for the project so far Greg, it's been a pleasure working with you. Congrats and welcome! On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone wrote: > Hi folks, > > Please welcome Greg Mann as the newest committer and PMC member of the > Apache

Re: Work group on Community

Thanks for kicking this off Vinod! (lists to bcc) I'm happy to join, I would add the following under this umbrella for now: --> Project PR (e.g. blog posts, twitter, etc) --> Events --> Website / documentation --> New contributor UX On Thu, Jun 15, 2017 at 10:57 AM, Vinod Kone

Re: [Proposal] Multiple Containers in Single Mesos Task

>From reading this, the motivation is that TaskGroup having 1 task per container "could create a scalability issue for a large scale Mesos cluster since many endpoints/operations scale with the total number of Tasks in the cluster." Is that the only motivation here? On Thu, Jun 15, 2017 at 11:45

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

a flaky test or a bug? On Thu, Jun 8, 2017 at 4:07 PM, Benjamin Mahler <bmah...@apache.org> wrote: > Vinod I think that's the getenv issue from: https://issues.apache.or > g/jira/browse/MESOS-6985 > > On Wed, May 17, 2017 at 5:57 PM, Till Toenshoff <toensh...@me.com>

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

Vinod I think that's the getenv issue from: https://issues.apache. org/jira/browse/MESOS-6985 On Wed, May 17, 2017 at 5:57 PM, Till Toenshoff wrote: > +1 > > Ran it through DC/OS builds and integration tests; > https://github.com/dcos/dcos/pull/1530 => all green > > On May 17,

Re: New YouTube channel to house working group recordings?

Is this the channel? https://www.youtube.com/channel/UC0wxLxgX8ilUn0m31lCpzAw If there are multiple channels, let me know, we can get them added to the website. Maybe here http://mesos.apache.org/documentation/latest/ presentations/ or on the community section. On Thu, May 18, 2017 at 6:47 PM,

Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

Thanks Yan! On Fri, Jun 2, 2017 at 10:45 AM, Yan Xu <y...@jxu.me> wrote: > +1 (binding) > > Ran it in a test cluster. > > --- > Jiang Yan Xu <y...@jxu.me> | @xujyan <https://twitter.com/xujyan> > > On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler <

<    1   2   3   4   5   6   7   8   9   10   >