Re: Build failed in Jenkins: mesos-reviewbot #6201

JPeach: That's correct. You had it right in the top level project, but the comparison was wrong in the libprocess check. Probably just a copy paste error, all fixed now! :-) Thanks for helping us move to more general macros! Joris On Thu, Jun 4, 2015 at 10:51 PM, James Peach wrote: > > > On Jun

Re: Introduction - Aditi

Hi Aditi, Please feel free to add me as a reviewer for these patches. I contributed part of Phase 1, and ended up looking ahead as to what would be required for the further phases. I'd be happy to review your patches! Joris On Thu, Jun 4, 2015 at 11:00 AM, Aditi Dixit wrote: > Hi all, > > I'm

Re: Apache Mesos Community Sync

Reminder: The Mesos Community Developer Sync will be happening today at 3pm Pacific. To participate remotely, join the Google hangout: https://plus.google.com/hangouts/_/twitter.com/mesos-sync On Thu, Jun 18, 2015 at 7:22 AM, Adam Bordelon wrote: > Reminder: We're hosting a developer community

Re: Review board: diff update

This is the worflow I usually share with people: Updating a review after comments: `git checkout master` `git fetch apache` `git rebase apache/master` 'git checkout ` `git rebase master` `git rebase -i HEAD^` (number of `^` based on how far back you want to pick `git add ` 'git rebase --c

Re: Mesos Style Guideline Adjustments

I will volunteer to update all the comments to wrap at 80 if we agree to keep the code base consistent. Naturally that is also my vote ;-) Joris > On Aug 8, 2015, at 1:40 PM, Michael Park wrote: > > An update on this topic since we covered it at the community developer sync. > > 1. We will

Re: Mesos 0.25.0

Hi Nik, I'd like to co-manage with you as I am invested in Maintenance Primitives :-) Joris On Thu, Aug 27, 2015 at 9:25 PM, Michael Park wrote: > Hey Niklas, > > As we discussed offline, I'm happy to co-manage or shadow this release. > > I would also like to add the beta follow-up features fo

Re: Mesos 0.25.0

Following in the footsteps of the dashboard for the 0.23.0 release, here is the Mesos 0.25.0 Release Dashboard This dashboard was very successful at reducing the time required to triage the first release candidate. Let's

Re: Do we still need to add InverseOffer support to Scheduler API?

Hi Qian, There is no current plan to add this to the old API. Those tickets were created pre-V1 API. Currently the goal is to encourage developers to use the V1 API to have access to new features such as maintenance primitives. Joris On Mon, Sep 14, 2015 at 10:22 AM, Qian AZ Zhang wrote: > > >

Re: Do we still need to add InverseOffer support to Scheduler API?

such > as offer and InverserOffers are initiatedby mesos master, the master need > notify the framework for those offers via the callbacks. Comments? > > Thanks, > > Guangya > > On Mon, Sep 14, 2015 at 10:42 PM, Joris Van Remoortere < > jo...@mesosphere.io> > wrote:

Re: [5/5] mesos git commit: Integer Precision for JSON <-> Protobuf conversions.

> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/2c277f1c > > Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/2c277f1c > > Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/2c277f1c > > > > Branch: refs/heads/master > > Commit: 2c277f1c0e0dc0a6618

Re: [5/5] mesos git commit: Integer Precision for JSON <-> Protobuf conversions.

M, Jie Yu wrote: >> >>> Joris, I am using CentOS6 with devtoolset-2 >>> >>> gcc version 4.8.2 20140120 (Red Hat 4.8.2-15) (GCC) >>> >>> I did a clean build (rebootstrap, reconfigure). >>> >>> - Jie >>> >>> >>&g

Re: Apache Mesos Community Sync

a >>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#heading=h.u1x3j7f3uixf> >>> . >>> >>> Thanks, >>> >>> On Thu, Jul 2, 2015 at 11:24 AM, Joris Van Remoortere < >>> jo...@mesosphere.i

Re: Mesos 0.25.0

; Thanks, > > Joris, MPark, and Niklas > > On Mon, Sep 14, 2015, 9:23 AM Joris Van Remoortere > wrote: > > > Following in the footsteps of the dashboard for the 0.23.0 release, > > here is the Mesos 0.25.0 Release Dashboard > > < > > > https://issues

Re: Volunteer for next release

+1 I can help triage with you :-) On Thu, Oct 1, 2015 at 1:44 AM, Till Toenshoff wrote: > Hi folks, > > Bernd and I would like to volunteer for managing the next release 0.26. > > The scope and ETA of 0.26 will be discussed today at the Mesos community > sync - hence more details on this will fo

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

+1 (binding) On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.25.0. > > > > 0.25.0 includes the following: > > > > > * [MESOS-1

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

+1 (binding) On Fri, Oct 9, 2015 at 5:36 PM, Niklas Nielsen wrote: > Hi all, > > Following up with an RC with the build fix suggested by Kapil: > > Please vote on releasing the following candidate as Apache Mesos 0.25.0. > > > > 0.25.0 includes the following: > > > --

Re: More Project Structure in JIRA

+1 sounds great! I like the idea of making epics more manageable and the ability to file JIRAs based on a design doc while still separating the Epic for the MVP from the further phases. > On Oct 15, 2015, at 10:11 AM, Bernd Mathiske wrote: > > Proposal: in extension of today’s limited two-leve

Re: RFC: license headers interfere with doxygen documentation (MESOS-3581)

+1 for (a). — *Joris Van Remoortere* Mesosphere On Tue, Oct 20, 2015 at 3:02 PM, Benjamin Mahler wrote: > +1 for (a), in this case the wide sweep only touches the license comments, > so it won't be disruptive to history. > > On Tue, Oct 20, 2015 at 11:59 AM, James Peach wrot

Re: minor doc fixes - do I need to have a JIRA ticket and a shepherd and a compass and a map of the pacific NW?

volunteer. I'm sorry the current impression of the contribution process is laborious. Mpark and I gave a talk about this at MesosCon EU. Hopefully the material will be available soon! Thanks for contributing! Joris — *Joris Van Remoortere* Mesosphere On Tue, Oct 20, 2015 at 11:36 PM, Erik

Re: Proposal: move towards #pragma and away from #include guards

+1 with all-at-once — *Joris Van Remoortere* Mesosphere On Thu, Nov 5, 2015 at 9:37 AM, Kapil Arya wrote: > +1. > > I think we should do it all at once as Artem mentioned. This doesn't really > affect the history (git-blame, etc.) because we are not touching code per > s

Re: Mesos Style Guideline Adjustments

tools. If there is more than some simple math involved, this may not be a viable solution. Joris — *Joris Van Remoortere* Mesosphere On Fri, Nov 6, 2015 at 11:10 AM, Benjamin Mahler wrote: > I raise this because there is a ton of value in keeping our codebase as > readable as possibl

Re: [2/2] mesos git commit: Added JSON parsing for Resources.

fixed — *Joris Van Remoortere* Mesosphere On Tue, Nov 10, 2015 at 9:53 PM, James Peach wrote: > > > On Nov 9, 2015, at 10:25 AM, m...@apache.org wrote: > > > > Added JSON parsing for Resources. > > > > > > [snip] > > > > http://git-wip-us

Re: `F()` vs `F(void)`

+1 — *Joris Van Remoortere* Mesosphere On Sun, Dec 13, 2015 at 11:39 AM, Benjamin Mahler wrote: > std::function becomes std::function? > > +1 > > On Sun, Dec 13, 2015 at 10:55 AM, Jie Yu wrote: > > > +1 > > > > On Sun, Dec 13, 2015 at 10:46 AM,

Fwd: [VOTE] Release Apache Mesos 0.26.0 (rc5)

+1 (binding) From: Till Toenshoff Date: Thu, Dec 10, 2015 at 2:55 PM Subject: [VOTE] Release Apache Mesos 0.26.0 (rc5) To: u...@mesos.apache.org, dev Hi friends, we did unfortunately, once again run into an issue that needed immediate attention (see vote on rc4), hence we have to ask for anot

Re: shepherd for MESOS-3909

I will. I think Joseph can (and already has) help review this. — *Joris Van Remoortere* Mesosphere On Tue, Dec 22, 2015 at 11:02 AM, James Peach wrote: > Hi all, > > Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-3909? > > Mesos modules depend on picojson, whic

Re: Change minimum supported version for GCC to 4.8.1

+1 (binding) I would like to propose that we bump our minimum supported version for gcc > from 4.8.0 to 4.8.1. The main motivation behind this is that there are at > least 2 outstanding reviews on RB that want to use ref-qualifiers < > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2439.

Re: Mesos 0.27.0

+1 On Wed, Jan 13, 2016 at 1:27 PM, Timothy Chen wrote: > Hi all, > > As we continue with the monthly release cadence, we should be cutting > a new release a month from the last one (12/16/15), which the next > version will be 0.27.0. > > MPark, Kapil and I are volunteering to be the release man

Re: Links in documentation

ng to external documentation. — *Joris Van Remoortere* Mesosphere On Thu, Jan 14, 2016 at 4:44 AM, Jörg Schad wrote: > Hi, > just a short note about links in our documentation. > In the current documentation we use three different ways to link between > different *.md pages: > 1. [lab

JIRA Shepherds

Hello Mesos developers, You may have noticed some churn in Jira recently around the shepherd assignment. Specifically, we have unassigned the shepherds for a bunch of projects. We did this in order to get a better sense of which projects are being actively shepherded versus having gone stale, and

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

-1 (binding) There is a bug with mutable resource math that surfaced in the allocator changes, but is also happening elsehwere. Mpark is currently working on a patch to disallow this behavior in general, and fix the current issues. https://issues.apache.org/jira/browse/MESOS-4030 On Wed, Jan 27,

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

Correction to my previous e-mail. The mutable resource bug is here: https://issues.apache.org/jira/browse/MESOS-4534 On Wed, Jan 27, 2016 at 11:57 AM, Joris Van Remoortere < joris.van.remoort...@gmail.com> wrote: > -1 (binding) > There is a bug with mutable resource math that sur

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

+1 (binding) Tested on Ubuntu 15.04: - Built with clang-3.6 and gcc-4.8. - Launched 1K agents. - Launched 100K tasks (slowly) on 100 agents. - Validated virtual memory set did not grow. - Validate UI was responsive. - Validate task recovery with 0.26 Master -> 0.27 Master

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

If we did feature based releases, we could hold the release for the documentation. Since we do time based releases, it so happened that the release went through before we could get the docs done. I'll be working on the docs shortly :-) — *Joris Van Remoortere* Mesosphere On Thu, Feb 4, 20

Re: Need shepherd for MESOS-4353 [Limit the number of processes created by libprocess]

ch as not having silent failure. — *Joris Van Remoortere* Mesosphere On Tue, Feb 9, 2016 at 9:02 PM, Maged Michael wrote: > https://issues.apache.org/jira/browse/MESOS-4353 > > Thanks. >

Re: Precision of scalar resources

+1 Thanks for taking this on Neil! — *Joris Van Remoortere* Mesosphere On Fri, Feb 12, 2016 at 11:25 PM, Neil Conway wrote: > tl;dr: > > If you use resource values with more than three decimal digits of > precision (e.g., you are launching a task that uses 2.5001 CPUs), >

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

+1 (binding) - systemd integration testing - upgrade path testing - launching and killing 10K tasks On Wed, Feb 17, 2016 at 6:52 PM, Jörg Schad wrote: > + 1 (non-binding) > > Mac OS: non-root: DockerFetcherPluginTest.INTERNET_CURL_FetchManifest >

Re: 答复: Question about "Framework directly access Meso agent"

evenly among agents. — *Joris Van Remoortere* Mesosphere On Wed, Feb 17, 2016 at 9:35 PM, Suteng wrote: > Alex, > We don't have test the performance of mesos. But we have develop a > framework in house, which is like a simplified mesos, use to schedule a > large number fine

Re: Enable compiler optimization by default?

+1 (binding) with the condition that we fix the flag mixing problem between CXXFLAGS and --enable-optimize --enable-debug, even if it is to disallow it for now. I want to avoid surprising behavior with implicit flags such as optimize: passing irrelevant CXXFLAGS magically turns it into a debug buil

Re: Anonymous modules running context - Another attempt

Hi Marco, It seems Kapil took a look at your reviews, and likely has context to understand whether this change makes sense. I would suggest that you clean up the style errors in the reviews, as there are still quite a few. Thanks! — *Joris Van Remoortere* Mesosphere On Fri, Feb 26, 2016 at 9

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

@Michael Browning: > > MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in > MESOS-4518] This is supposed to be fixed in this release. It is concerning that this came up. Can you verify this and provide logs to Kevin Klues? — *Joris Van Remoortere* Mesosphere On Tue, Mar 1

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

+1 (binding) Greg's upgrade scripts & CI results On Fri, Mar 4, 2016 at 11:30 AM, Vinod Kone wrote: > +1 (binding) > > On Tue, Mar 1, 2016 at 5:03 PM, Kevin Klues wrote: > > > I committed a fix for this in: > > > > > https://github.com/apache/mesos/commit/42f746937233349660c687ea7a66cc0a7887166

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

+1 (binding) Greg's upgrade scripts & CI results On Tue, Mar 1, 2016 at 4:37 PM, Greg Mann wrote: > I was also able to successfully test a simple upgrade scenario between > 0.24.2-rc1 and 0.25.1-rc1 using Niklas's upgrade testing script, which I've > modified slightly and reposted here: https://

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

+1 (binding) On Mon, Feb 29, 2016 at 3:24 PM, Greg Mann wrote: > +1 (non-binding) > > `sudo make check` on Ubuntu 14.04, using gcc with libevent and SSL enabled. > All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, > which is a known failure in 0.24. > > Cheers, > Greg > > >

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

e/mesos/commits/0.25.1-rc1/src/tests/master_tests.cpp > >> > > >> > > >> > https://github.com/apache/mesos/commits/0.24.2-rc1/src/tests/master_tests.cpp > >> > > >> > Just not: > >> > > >> > > >> > https://gi

Re: Compile failure

e to install the correct version: $ sudo cat > /etc/yum.repos.d/wandisco-svn.repo <http://opensource.wandisco.com/centos/7/svn-1.9/RPMS/$basearch/ gpgcheck=1 gpgkey=http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco EOF — *Joris Van Remoortere* Mesosphere On Mon, Mar 7, 2016 at 7:01 AM, Walt

Re: Negative durations

an absolute value, then it would be a bug. To represent infinity we currently wrap the Duration with an Option. The None state represents infinity. You can find this in the protobufs. — *Joris Van Remoortere* Mesosphere On Wed, Mar 9, 2016 at 11:29 PM, Alexander Rojas wrote: > IMO durations

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

The SHAs rarely exist on HEAD because we tend to cherry-pick bug fixes into release candidates. I'm all for using branches in the repository to put together the release candidates, as well as have committers consider their bug fixes for some N number of backport (future LTS) releases. As Kevin an

Re: RFC: RevocableInfo Changes

* we would never want that concept in Mesos. — *Joris Van Remoortere* Mesosphere On Sun, Mar 20, 2016 at 8:33 PM, Klaus Ma wrote: > Here's some input :). > > If throttling is tolerable but preemption is not, how would that be > expressed? (Is that supported?) > [Klaus]: It&#

Re: Filing bugs and flaky test tickets

gadget to the JIRA release board that lists all issues that are unresolved and affecting the previous release, in order of severity. — *Joris Van Remoortere* Mesosphere On Tue, Mar 22, 2016 at 7:15 AM, Benjamin Mahler wrote: > Folks, > > Our JIRA volume is very high and I'm finding

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

lve with the current tag-only approach. Joris and Jie > seem to be hinting at there being a lack of visibility into the progress of > RCs. Is that the issue we're trying to solve? Collaboration on RC's? I > haven't done a release in quite some time so it would be great to

Re: Ordering guarantee of future.onAny callbacks

ad setting the future to true. I'd rather discuss and fix the problem, than try to enforce avoiding this case. Thoughts? — *Joris Van Remoortere* Mesosphere On Tue, Mar 29, 2016 at 2:50 AM, Jie Yu wrote: > Hi, > > While digging a bug reported in, I realized an assumption we shou

Re: Ordering guarantee of future.onAny callbacks

nefits of executing multiple `.onAny` calls in parallel in the future (if we ever need to) outweigh the inconsistency in the API regarding ordered execution of certain chains (At least as the API is currently designed). — *Joris Van Remoortere* Mesosphere On Wed, Mar 30, 2016 at 12:25 AM, Benjamin

Re: docker, systemd, and cfs_quota

systemd? Joris — *Joris Van Remoortere* Mesosphere On Fri, Apr 15, 2016 at 6:00 PM, Michael Browning wrote: > Hi all, > > We've run into an interesting issue with Docker and systemd that's > hampering our attempts to use cfs_quota for CPU isolation with Docker > cont

Re: Mesos Community Sync Notes

That is the plan, I think it just hasn't been done yet :-) — *Joris Van Remoortere* Mesosphere On Thu, Apr 21, 2016 at 9:20 PM, Qian Zhang wrote: > In that wiki, can we also put the corresponding JIRA ticket link there so > that folks can take a close look at the projects they are

Re: How to record time elapsed of a set of async functions operation?

To be clear, BenM's example will result in the total wall-clock time for the chain to complete, rather than the sum of time actually spent in those functions. — *Joris Van Remoortere* Mesosphere On Fri, Apr 22, 2016 at 4:26 PM, Benjamin Mahler wrote: > Here's an example of using

Re: Default value of Filter.refuse_seconds

After https://github.com/apache/mesos/commit/447d814ac80e67f30a0ffe2ee6047d85dc8fc383 the refuse_seconds should not be as dangerous as it used to be. This was backported to 0.24 and above recently. Without the backported patch the filter may never take effect when the allocation takes longer than t

Re: Rack awareness support for Mesos

+dev. @Fan, I responded on the JIRA with some next steps. Thanks for bringing this up! — *Joris Van Remoortere* Mesosphere On Tue, Jun 7, 2016 at 12:58 PM, james wrote: > On 06/07/2016 09:57 AM, Du, Fan wrote: > >> >> >> On 2016/6/6 21:27, james wrote: >> >

Re: Apply for assignment of jira MESOS-5425

Hello! Thanks for sharing your feedback regarding the range performance. Indeed as you partition things like agent ports heavily this can be detrimental. We have looked at this in the past, and the right thing to do is indeed to use the interval set in Stout. That being said, the reason we have

Re: Rack awareness support for Mesos

and which values are allowed to change vs. not. — *Joris Van Remoortere* Mesosphere On Tue, Jun 14, 2016 at 10:04 AM, Aaron Carey wrote: > #3 would be very helpful for us. Also related: > > https://issues.apache.org/jira/browse/MESOS-3059 > > -- > > Aaron Carey > Prod

Re: Rack awareness support for Mesos

your interest is in the determination of the values, as opposed to their propagation, I would just urge that you keep in mind that we may (as a project) not want to support this information as the current string attributes. — *Joris Van Remoortere* Mesosphere On Tue, Jun 14, 2016 at 3:02 PM, D

Re: Multiple framework DRF tuning

Your e-mail seems truncated or mangled in some way (at least for me). Could you please resend it? — *Joris Van Remoortere* Mesosphere On Tue, Jun 14, 2016 at 10:00 PM, meghdoot bhattacharya < meghdoo...@yahoo.com.invalid> wrote: > > > I wanted to follow up on 2 issues that w

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

With this 4th sorter approach, how does quota work for scarce resources? — *Joris Van Remoortere* Mesosphere On Thu, Jun 16, 2016 at 11:26 AM, Guangya Liu wrote: > Hi Ben, > > The pre-condition for four stage allocation is that we need to put > different resources to different so

Re: Multiple framework DRF tuning

nsequences from doing this. — *Joris Van Remoortere* Mesosphere On Wed, Jun 15, 2016 at 8:33 PM, meghdoot bhattacharya < meghdoo...@yahoo.com.invalid> wrote: > Resending with fixed links. > > I wanted to follow up on 2 issues that we discussed few years back on the > below blog des

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

@Fan, In the community meeting a question was raised around which frameworks might be ready to use this. Can you provide some more context for immediate use cases on the framework side? — *Joris Van Remoortere* Mesosphere On Fri, Jun 17, 2016 at 12:51 AM, Du, Fan wrote: > A couple of ro

Re: Failed to shutdown socket with fd xxx

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

Re: Failed to shutdown socket with fd xxx

ition 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&am

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 o

Re: Failed to shutdown socket with fd xxx

bout the isolation (you likely do in production), then the only remedy is to restart them. — *Joris Van Remoortere* Mesosphere On Mon, Jun 20, 2016 at 4:45 AM, Qiang Chen wrote: > Thanks @Haosdent for the link to explain the shutdown errors. so I can > ignore this... > > @Joris, > >

Re: Persistent volume ownership issue

he App tried to create /Database-backups/ ? Only the framework as its original user would be able to do that? — *Joris Van Remoortere* Mesosphere On Tue, Jun 21, 2016 at 8:25 AM, Jie Yu wrote: > Hi folks, > > Currently, the ownership of the persistent volumes are set to be the same >

Re: Mesos CLI

+1 for maintaining in repo. +1 for C++. Are the tools in libprocess not sufficient to make this easy to write? What is missing that would make it easier to write in C++? — *Joris Van Remoortere* Mesosphere On Wed, Jun 22, 2016 at 2:24 AM, Zhou Z Xing wrote: > +1 for keeping it in Mesos r

Re: Mesos CLI

n experts have time. This is a trade-off we should consider. The best option may still be for it to be in Python, this is why I'm asking if there are particular things that our helper libraries don't provide which you are leveraging in python. — *Joris Van Remoortere* Mesosphere On Thu,

Re: [Protobuf] Why do we mark field as 'required'

I think it would be great to comment in place e.g. `/* required */ optional `. It's difficult enough as is to extract the semantics out of the current Protos. The required helped document which fields were actually required. — *Joris Van Remoortere* Mesosphere On Thu, Jun 23, 2016 at 2:

Re: "sleep" in a libprocess Process

Hi Hans, If you delay, and then the lambda that you schedule is a `defer` on to the same process, then this accomplishes what you want. The one caveat is that other functions may be invoked on your actor process in the mean time. — *Joris Van Remoortere* Mesosphere On Tue, Jun 28, 2016 at 1:14

[Action Required] Stale Reviews

Hello developers, Over the last year we've accumulated a significant review backlog. Over the past month it has been floating around ~600 reviews. It would be of great help if you could look through your personal list (Dashboard -> Outgoing -> Open) and identify reviews that are *no longer releva

Re: [Action Required] Stale Reviews

ugh on them with the contributor. On Wed, Jun 29, 2016 at 8:17 PM, Tomek Janiszewski wrote: > How about running CI on all reviews. If patch is stale it probably can't be > applied, CI will post bad patch and if nobody do any action on that review > we can close it. > > śr.

Re: Apply for further review for 48593

I'll take another look at this tomorrow with Joseph. Thanks for your hard Work! — *Joris Van Remoortere* Mesosphere On Fri, Jul 1, 2016 at 3:59 AM, Yan Yan YY Hu wrote: > > Hi, could anyone help to make further review on 48593( > https://reviews.apache.org/r/48593/). It is an i

Re: MESOS-4694

h reconsidering whether we need to do this hack. — *Joris Van Remoortere* Mesosphere On Thu, Jul 7, 2016 at 10:15 AM, Guangya Liu wrote: > Hi Ben and Dario, > > The reason that we have "SUPPRESS" call is as following: > 1) Act as the complement to the current REVIVE call.

Re: MESOS-4694

slack?) when you feel a sufficient explanation is updated in the patch and I'll schedule time to review them. Joris — *Joris Van Remoortere* Mesosphere On Thu, Jul 7, 2016 at 7:20 PM, Dario Rexin wrote: > A bit more context: > > We have a very high number of frameworks on our clus

Re: [Action Required] Stale Reviews

when they don't make sense, or have been replaced. Many of the ones I closed ended up being irrelevant. Thanks for all your contributions. I will be engaging with the committers to get as many of the remaining patches committed as is possible. Joris — *Joris Van Remoortere* Mesosphere On Wed,

Re: MESOS: Improve the performance of Resources.

only quantities in the Sorter, and that using the existing form of Resources would have led to a grinding halt if a reservation were made on every machine. Is there a regular call that is scheduled to discuss this? I think there are some other folks also working on benchmarks and interested in the dis

Re: MESOS: Improve the performance of Resources.

callgrind results to find other bottlenecks mentioned earlier in the thread. — *Joris Van Remoortere* Mesosphere On Tue, Jul 12, 2016 at 2:26 AM, Guangya Liu wrote: > Hi Joris, > > For `2x` number, can you please show more detail for how did you do and > evaluate the test? How did

Re: Mapped diagnostics context - Adding internal Mesos IDs as context to the logs

ad-safe. > // > GOOGLE_GLOG_DLL_DECL void SetLogFilenameExtension( > const char* filename_extension); @benm @vinod @benh what are your thoughts on actually doing it? — *Joris Van Remoortere* Mesosphere On Tue, Oct 4, 2016 at 2:39 PM, Zameer Manji wrote: > I don't know

Re: Separate Compilation of Tests

tually can become IO bound. There are ways to get around that too. There have been times where an optimized build has been faster than a debug build. Joris — *Joris Van Remoortere* Mesosphere On Tue, Sep 27, 2016 at 6:25 PM, Michael Park wrote: > On Tue, Sep 27, 2016 at 12:21 PM, Alexander Roj

Re: Mapped diagnostics context - Adding internal Mesos IDs as context to the logs

ID, Master ID, etc. — *Joris Van Remoortere* Mesosphere On Wed, Oct 5, 2016 at 11:34 AM, Benjamin Hindman wrote: > How does adding the filename extension help with the context problem? > > On Wed, Oct 5, 2016 at 6:14 AM, Joris Van Remoortere > wrote: > >> This is technic

Re: [E] Re: Require GCC >= 4.9

larger reasons (for example when we wanted c++11) we'll need to propose the change and provide some deprecation period regardless. — *Joris Van Remoortere* Mesosphere On Tue, Oct 11, 2016 at 4:53 AM, Evers Benno wrote: > To be honest, I still think it's a pretty big pain to req

Re: A Plan for Mesos Community Syncs

+1 — *Joris Van Remoortere* Mesosphere On Thu, Oct 13, 2016 at 1:38 PM, Vinod Kone wrote: > Huge +1. Thanks for taking ownership of this. > > On Thu, Oct 13, 2016 at 1:34 PM, Michael Park wrote: > > > I would like to try to get the community syncs back on track. They h

Re: Non-checkpointing frameworks

ng experience for them to find out that is not the case. — *Joris Van Remoortere* Mesosphere On Fri, Oct 14, 2016 at 3:11 PM, Neil Conway wrote: > Hi folks, > > I'd like input from individuals who currently use frameworks but do > not enable checkpointing. > > Backgroun

Re: Allowing both CommandInfo and ExecutorInfo on TaskInfo

executors then it would be great for there to be standard way to pass command information to them. The current model works well in a 1-1 mapping between framework and executor binaries. In a world where that is 1-N it means all N executors have to use the same method of passing the command. — *Joris Van

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

-1 My understanding after speaking with BenM is that the fix for https://issues.apache.org/jira/browse/MESOS-6457 should be straight forward. I don't think the cost of debugging and fixing production systems if they run into this is worth skipping an easy fix. I have re-targeted the JIRA to 1.1.0

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

-1 Based on my message in the 1.1.0 vote: My understanding after speaking with BenM is that the fix for https://issues.apache.org/jira/browse/MESOS-6457 should be straight forward. I don't think the cost of debugging and fixing production systems if they run into this is worth skipping an easy f

Re: Proposal for mesos replicated log improvements

I think I'm missing why we would spend energy controlling the leveldb compaction. I thought leveldb was used for convenience, and its log structured merge algorithm was just a consequence. Why not spend energy writing an append only file as opposed to optimizing compaction of an algorithm we d

Re: Allowing both CommandInfo and ExecutorInfo on TaskInfo

still seem like an issue if it's not a requirement but just a broadening of possibilities? — *Joris Van Remoortere* Mesosphere On Wed, Nov 2, 2016 at 1:49 PM, Zameer Manji wrote: > Joris, > > You make a good point. However, I'm not convinced that `CommandInfo` should > be

Re: Failed to launch spark jobs on mesos due to "hadoop" not found

Switch to the user that the agent is running as, and the directory from which it is executing and ensure that you can find hadoop. For example by running `which hadoop`. This may be a PATH or JAVA_HOME issue? — *Joris Van Remoortere* Mesosphere On Thu, Nov 10, 2016 at 6:29 AM, Yu Wei wrote

Re: Duplicate task IDs

x27;m wondering why a multi-hashmap is not sufficient. This would be clear if you were explicitly *trying* to get rid of duplicates of course :-) Thanks, Joris — *Joris Van Remoortere* Mesosphere On Fri, Dec 9, 2016 at 7:08 AM, Neil Conway wrote: > Folks, > > The master stores a cac

Re: Duplicate task IDs

only catch some of the manifestations. — *Joris Van Remoortere* Mesosphere On Mon, Dec 12, 2016 at 7:56 AM, Neil Conway wrote: > Hi Joris, > > Fair point: I didn't deliberately set out to change the behavior for > duplicate task IDs. Rather, it was a consequence of switc

Re: Building on OS X 10.12

safe? Joris — *Joris Van Remoortere* Mesosphere On Mon, Dec 5, 2016 at 1:16 PM, James Peach wrote: > > > On Dec 2, 2016, at 10:54 PM, Jie Yu wrote: > > > > Another tip. If you are on macOS sierra, you might notice the linking is > > extremely slow using the defau

Re: MESOS-6233 Allow agents to re-register post a host reboot

e in the agent configuration? I think we highly recommend that you do this in production to prevent accidental incompatibility of resources even without an actual hardware change. Historically there were some issues reported where the kernel reported a slightly different amount of memory after reboo

thread_local supported on Apple

to whether requiring this toolchain update is acceptable, and if we need a deprecation period or if we can just make this change now. I am leaning towards no deprecation period as I am not aware of production environments running on systems that define `__APPLE__`. — *Joris Van Remoortere

Re: thread_local supported on Apple

Is my understanding incorrect regarding the ability to upgrade the compiler version on Yosemite and El Capitan without requiring a full system upgrade? @Mpark are you making a case for not updating to `thread_local` just yet? — *Joris Van Remoortere* Mesosphere On Fri, Dec 16, 2016 at 11:11 AM

Re: Structured logging for Mesos (or c++ glog)

@Zhitao are you looking specifically for structure or just for tagging? glog does already have support for custom tags in the header. I don't know if this is enough for your use case though. — *Joris Van Remoortere* Mesosphere On Mon, Dec 19, 2016 at 9:58 AM, James Peach wrote: > >

  1   2   3   4   5   >