Re: how to change mesos resources

Have you tried the remedy steps included in the error message? To remedy this do as follows: Step 1: rm -f /tmp/mesos/meta/slaves/latest This ensures slave doesn't recover old live executors. Step 2: Restart the slave. On

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

+1 (binding) Tested on ASF CI. On Sun, Mar 13, 2016 at 4:33 PM, Michael Park wrote: > +1 (binding) > > Internal CI results with the corresponding JIRA tickets for the failed > tests: > > CentOS 6 (non-SSL): > -

Re: How to make full version available in /version endpoint

Not currently, no. What's your use case? On Wed, Mar 23, 2016 at 3:50 PM, Zhitao Li wrote: > Hi, > > Has anyone brought up the possibility of making the full version > (i.e. 0.28.0-2.0.16.debian81a) show up in the the /version endpoint? > > For example, when we are using

[RFC] Mesos Releases and Support

Hi folks, There has been some interest recently about Mesos releases and support policy. As promised, I spent some time thinking about this and written my thoughts down in a doc. https://docs.google.com/document/d/1A8MglUWST6pWan3cVw98v8uxTPew8RMKxxrRqiSENM0/edit?usp=sharing Please take a look

Re: HTTP API

Thanks for the interest! We are actively working to make the Framework v1 API stable. We've made quite a few improvements/fixes to the Scheduler v1 API since 0.24.0. We've also introduced Executor v1 API in 0.28.0. Both are in *experimental* state. There are still things left to do to make the

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

uilt 0.28.0-rc1 with this patch and can confirm that it fixes it >>> as expected. >>> >>> Apologies for not bringing this to attention earlier. >>> >>> Thanks all, >>> Dan >>> >>> -Original Message- >>> From: Vin

Re: 0.28.0 release

Release vote sent. The soft lock is released as well. Commit away! On Thu, Mar 3, 2016 at 4:58 PM, Timothy Chen <tnac...@gmail.com> wrote: > Sorry I pushed a quick typo fix before seeing this email. > > Tim > > On Thu, Mar 3, 2016 at 4:15 PM, Vinod Kone <vinodk...@apache

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

On Thu, Mar 3, 2016 at 5:43 PM, Vinod Kone <vinodk...@apache.org> wrote: > Tue Mar 10 17:00:00 PST 2016 Sorry. This should be Mar 8th not 10th.

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

cluded in the > .1 rc > > On Mon, Feb 29, 2016 at 2:27 PM, Vinod Kone <vinodk...@apache.org> wrote: > >> Looks like the ASF CI builds for CentOS7 are failing because they are >> unable to find JAVA_HOME. Couldn't tell if it's an issue with the docker >> build scrip

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

t of ReserveResources and CreateVolume >> ACLs to `roles`. >> * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1 >> Scheduler API. > > > MESOS-4712 is included twice. > > On Fri, Mar 4, 2016 at 1:25 PM, Vinod Kone <vinodk...@apache.org> wr

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

I think this was supposed to refer to https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md @Jie ^^ ? On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker < sschlans...@opentable.com> wrote: > > > On Mar 3, 2016, at 5:43 PM, Vinod Kone <vinodk...@apache.org&

Need CHANGELOG updates

Hi guys, The 0.28.0 release is currently blocked on the updates to CHANGELOG. Basically I'm looking for shepherds/owners of feature tickets to add a blurb in the CHANGELOG for their tickets. The big ticket items that went into 0.28.0 that I know of --> net_cls_isolator --> floating point math

Re: Making 'curl' a prerequisite for installing Mesos

sgtm On Thu, Mar 3, 2016 at 10:01 AM, Jie Yu wrote: > Neil, thanks for the comments and the pointer! > > Just looked at the curl_multi_xxx() API. Yeah, I think we should be able > to use that API in our async environment. But we need to hook this with > our underlying

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

rg/jira/browse/MESOS-4370 > RB# 43093: https://reviews.apache.org/r/43093/ > > I've built 0.28.0-rc1 with this patch and can confirm that it fixes it as > expected. > > Apologies for not bringing this to attention earlier. > > Thanks all, > Dan > > -Original Messa

NYC Meetup on Mar 9th

Hi, If you are in the NYC area and are a Mesos enthusiast, you might be interested in the upcoming meetup in NYC. Please visit http://www.meetup.com/Apache-Mesos-NYC-Meetup/events/229086077/ for more details. Looking forward to the meetup, Vinod P.S: @MPark, can you please add this to our

Re: [RFC] Mesos Releases and Support

on LTS until we get some experience with the new release and patch policies. On Fri, Mar 25, 2016 at 12:21 PM, Vinod Kone <vi...@mesosphere.io> wrote: > Hi folks, > > There has been some interest recently about Mesos releases and support > policy. As promised, I spent some t

Re: Unstability on Mesos 0.27

Hey Gabriel, Could you share more details on what the crashes are and what your setup is (docker containerizer?). Any logs (master, agent, application) that can shed light would be useful to diagnose. On Wed, Mar 16, 2016 at 5:12 PM, Alfredo Carneiro < alfr...@simbioseventures.com> wrote: >

Re: Mesos agents across a WAN?

This is great info Evan, especially coming from a production experience. Thanks for sharing it ! On Thu, Mar 31, 2016 at 1:49 PM, Evan Krall wrote: > On Wed, Mar 30, 2016 at 6:56 PM, Jeff Schroeder < > jeffschroe...@computer.org> wrote: > >> Given regional bare metal Mesos

Re: Run Mesos without master being able to open connections to slaves

On Mon, Apr 25, 2016 at 8:35 AM, Elouan Keryell-Even < elouan.kery...@gmail.com> wrote: > So I'd be glad to have some insight from you guys about if it is possible, > in one way or another, to make Mesos work without the Master being able to > initiate connections to slaves. I just need to be

Re: Reconnected slaves not sending resource offers?

On Mon, Apr 25, 2016 at 8:40 AM, Thomas Petr wrote: > The only thing that ended up fixing the situation was bouncing our > scheduler (~10 minutes after the restarted slaves joined the cluster) -- > the act of failing over the framework appeared to "recover" the missing >

Re: Mesos Web UI

Adam, since you committed this, feel free to backport it to the relevant stable branches (26.x, 27.x, 28.x). They will be included in the next patch releases. On Fri, Apr 29, 2016 at 9:31 AM, Gilbert Song wrote: > Julian, since the fix was after 0.28, could you try it

Re: Change the role of a framework

I think what you did seems correct. On Thu, Apr 28, 2016 at 6:31 PM, Shuai Lin wrote: > Hi list, > > For some reason I need to change the role of an existing framework > (marathon) from the default role "*" to a specific role, say "services", I > don't find any existing

Design doc for v1 Operator API

Hi folks, Here is the design doc for the v1 Operator API. Please take a look and give us feedback. https://docs.google.com/document/d/1XfgF4jDXZDVIEWQPx6Y4glgeTTswAAxw6j8dPDAtoeI/edit?pref=2=1# Thanks, Vinod

Re: Setting constraints

There is no flexible/dynamic way to ensure that a particular task runs on every agent in the cluster. If you are ok with static configuration, you can set aside resources for a role on every agent by using the resources flag (e.g, --resources="cpus(system):2;cpus(*): 10" on an agent with 12

Re: mesos website workgroup

com) wrote: > > I'm happy to help, > > Tim > > On Tue, May 17, 2016, 6:01 AM Freddy Ayuso-Henson <faay...@gmail.com> > wrote: > >> I’m interested in contributing. >> >> >> >> From: Vinod Kone <vinodk...@apache.org> <vinod

Re: Error on Teardown attempt: Framework is not connected via HTTP

That's not the endpoint you want (that's for frameworks to use). You want /teardown endpoint (that's for operators).

Re: kafka-mesos still refusing to launch brokers on one cluster

Is there nothing in the mesos master logs about this scheduler trying to connect/register? If not, the registration message from the scheduler is not making it to the master. Are there any firewall rules between the scheduler host and master host?

Re: kafka-mesos still refusing to launch brokers on one cluster

On Tue, Apr 19, 2016 at 11:24 AM, Justin Ryan wrote: > Marathon has no trouble registering a framework and launching jobs on this > cluster, only kafka-mesos. :/ > > Are both these frameworks binding to the same IP/interface? Does anyone of them use any LIBPROCESS_IP or

Re: kafka-mesos still refusing to launch brokers on one cluster

On Mon, Apr 18, 2016 at 12:32 PM, Justin Ryan wrote: > So, test is working again, but prod is still and has consistently been dead What do the master/agent/scheduler logs say regarding kafka tasks?

Re: 0.28.2

Patch releases are for bug fixes ugly only. So you have to wait for the next stable release. @vinodkone > On May 25, 2016, at 5:52 AM, June Taylor wrote: > > We recently upgraded to 0.28.1 and were looking for the feature where a role > can be specified to mesos-execute. This

1.0 Release Candidate

Hi folks, As discussed in the previous community sync, we plan to cut a release candidate for our next release (1.0) early next week. 1.0 is mainly centered around new APIs for Mesos. Please take a look at MESOS-338 for blocking issues. We got

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

in CentOS 7.2 > * make check in Ubuntu 14.04 > * test upgrade from 0.28.2 to 1.0.0-rc4 > > > On Tue, Jul 26, 2016 at 8:33 AM, Kapil Arya <ka...@mesosphere.io> > > wrote: > > > One can find the deb/rpm packages here: > > http://open.mesosphere.com/downloads/me

[VOTE] Release Apache Mesos 1.0.0 (rc3)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a majority of at least 3 +1 PMC votes are cast.* 1.0.0 includes the following:

[RESULT][VOTE] Release Apache Mesos 1.0.0 (rc4)

os-1.0.0.jar has been released to: https://repository.apache.org The website (http://mesos.apache.org) will be updated shortly to reflect this release. Thanks, On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone <vinodk...@apache.org> wrote: > Hi all, > > > Please vote on rel

Re: [RESULT][VOTE] Release Apache Mesos 1.0.0 (rc4)

The 1.0 blog post is up: http://mesos.apache.org/blog/mesos-1-0-0-released/ Thank you all for making this possible! @vinodkone > On Jul 27, 2016, at 7:39 AM, Vinod Kone <vinodk...@apache.org> wrote: > > Hi all, > > The vote for Mesos 1.0.0 (rc4) has passed wit

Re: Possible authentication bug

On Thu, Jul 21, 2016 at 4:49 PM, Douglas Nelson wrote: > Just out of curiosity, is there a rough ETA for the stable release of > 1.0.0? Or is anyone currently using rc2 in production? > I'm hoping to cut RC3 later today or tomorrow and barring any -ve votes do the official

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

Looks like we missed a cherry pick. I'm cancelling this vote and spinning up rc4. On Fri, Jul 22, 2016 at 2:24 PM, Vinod Kone <vinodk...@apache.org> wrote: > Hi all, > > > Please vote on releasing the following candidate as Apache Mesos 1.0.0. > > *The vote is open until

[VOTE] Release Apache Mesos 1.0.0 (rc4)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a majority of at least 3 +1 PMC votes are cast.* 1.0.0 includes the following:

Re: Enabling basic access authentication

We separated out the default authentication mode for read only (default: no authn) and read-write (default: authn) endpoints. Since the webui only depends on the read-only endpoints you need to explicitly enable authn for read-only endpoints if you need authn. See

1.0.1 release

Hi, As discussed on the 1.0 voting thread, we plan to cut a 1.0.1 as early as this week. So if you have anything that needs to absolutely go into the patch release, please work with your shepherd and get it landed on trunk and backported to the 1.0.x branch. Thanks,

[VOTE] Release Apache Mesos 1.0.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.1. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.1-rc1

Re: test

Don't sweat about the test email. Not a big deal. Welcome to the community! On Wed, Jul 13, 2016 at 1:51 PM, Rahul Palamuttam wrote: > I'm truly sorry. > Just kept getting several message denied errors, until I realized I needed > to send a reply to user-subscribe. > I

Re: Possible authentication bug

Might be related to MESOS-2043 ? Can you paste master and agent logs? On Mon, Jul 18, 2016 at 3:13 PM, Douglas Nelson wrote: > I have SSL enabled for mesos and for the most part everything seems to be > working fine. But

Re: mesos agent not recovering after ZK init failure

On Fri, Jul 15, 2016 at 11:31 AM, Sharma Podila wrote: > We had this issue happen again and were able to debug further. The cause > for agent not being able to restart is that one of the resources (disk) > changed its total size since the last restart. However, this error

Re: How to send a task to a running framework?

Are you asking how users can submit their tasks to your custom framework? Your framework should probably expose an API for that. On Fri, Jul 8, 2016 at 4:30 AM, Bryan Fok wrote: > Hi all > > After I have my custom framework running in , for instance, a python > process

[VOTE] Release Apache Mesos 1.0.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. 1.0.0 includes the following: * Scheduler and Executor v1 HTTP APIs are now considered stable. * [MESOS-4791] -

Support for tasks groups aka pods in Mesos

Hi folks, One of the most requested features in Mesos has been first class support for managing pod like containers. We finally have some time to focus and shepherd this work. The epic tracking this work is : https://issues.apache.org/jira/browse/MESOS-2449 Design doc:

Re: Support for tasks groups aka pods in Mesos

Sorry, sent the wrong link earlier for design doc. Design doc: https://issues.apache.org/jira/browse/MESOS-6009 > Direct link: https://docs.google.com/document/d/1FtcyQkDfGp-bPHTW4pUoqQCgVlPde936bo-IIENO_ho/edit#heading=h.ip4t59nlogfz

Re: GPU channel on slack

Mind updating https://github.com/apache/mesos/blob/master/docs/working-groups.md with this info? On Thu, Jun 30, 2016 at 8:44 AM, Kevin Klues wrote: > If you are interested in the ongoing GPU work on Mesos, please join the > #gpus channel at mesos.slack.com. The big

Re: 1.0.0 RC2

=12328715 On Tue, Jun 21, 2016 at 11:48 AM, Vinod Kone <vinodk...@apache.org> wrote: > There are still 8 outstanding issues, including 1 blocker. We are waiting > for these to land for RC2. > > > On Fri, Jun 17, 2016 at 5:11 PM, Vinod Kone <vinodk...@apache.org> wrote: &

[VOTE] Release Apache Mesos 1.0.3 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.3. 1.0.3 includes the following: * [MESOS-6052] - Unable to launch containers on CNI networks on CoreOS * [MESOS-6142] -

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

+1 (binding) Tested on ASF CI. *Revision*: 5d4c9962930c3f5c08e802caff40b670424cb091 - refs/tags/1.1.1-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Success]

[RESULT][VOTE] Release Apache Mesos 1.0.3 (rc2)

Hi all, The vote for Mesos 1.0.3 (rc2) has passed with the following votes. +1 (Binding) -- Vinod Kone Adam Bordelon Kapil Arya There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.0.3

Re: Framework stops to receive the heartbeats and events and gets removed from master

Can you paste the logs or master and framework? @vinodkone > On Jan 23, 2017, at 8:05 AM, Vova Shelgunov wrote: > > Hi, > > I faced a very strange situation with my framework that talks to mesos master > via Scheduler HTTP API: > > Sometimes my framework stops to receive

Welcome Neil Conway as Mesos Committer and PMC member!

Hi folks, Please welcome Neil Conway as the newest committer and PMC member of the Apache Mesos project. Neil has been an active contributor to Mesos for more than a year now. As part of his work, he has contributed some major features (Partition aware frameworks, floating point operations for

Re: Question: Modify mesos agent to add custom resources that change dinamically

Don't think that's possible today and I cannot think of easy workarounds for it. On Thu, Feb 9, 2017 at 1:39 AM, Carnero Iglesias, Javier < javier.carn...@atos.net> wrote: > Hi guys, I’ve posted in StackOverflow a *question* >

Re: Framework stops to receive the heartbeats and events and gets removed from master

No problem. Glad you figured out. @vinodkone > On Jan 23, 2017, at 8:38 AM, Vova Shelgunov wrote: > > Yes, it works. Sorry for troubling, the first time when I looked at the logs > I did not notice that failover_timeout is zero. > > 2017-01-23 19:27 GMT+03:00 Vova

Mesos 1.0.3 release

Hi folks, I'm planning to cut 1.0.3 release tomorrow. If you need anything that needs to be backported, please mark the tickets as such. Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12330112 Thanks, Vinod

Re: Mesos logging

Did you figure this out? AFAICT, the LOG(INFO) line should be printed in agent logs. What agent flags are you using? On Tue, Aug 9, 2016 at 8:19 AM, Hendrik Haddorp wrote: > I saw a few "Running ..." log entries from the docker support code but > they seem to be all

Fwd: REMINDER: MesosCon Asia’s CFP Deadline is September 9! Submit your Proposal Today

Hi folks, Just a friendly reminder that the CFP for MesosCon Asia is fast approaching! If you were planning to submit a talk please do so ASAP. If you weren't, please do :) Thanks, Vinod -- Forwarded message -- From: Linux Foundation Events Date:

Re: Setting log path for mesos java client library

Looks like Mesos logging flags for these override the corresponding GLOG related flags.

Re: Updating ExecutorInfo after framework failover or best practice

We cannot easily make ExecutorInfo mutable because there might be existing tasks with executors with the old ExecutorInfo. If there are two different ExecutorInfos for the same ExecutorID it gets confusing for Mesos (e.g., SHUTDOWN executor id 'foo' kills which executor?). One possible solution

1.0.2 release

Hi, As the Release Manager for 1.0, I'm responsible for all subsequent patch releases. I'm planning to cut the next patch release (1.0.2) within a week. So, if you have any patches that need to get into 1.0.2 make sure that either it is already in the 1.0.x branch or the corresponding ticket has

Re: 1.0.2 release

Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329719 I'm waiting for 2 issues to be resolved. Once that's done, I'll start prepping the release. On Wed, Oct 5, 2016 at 4:11 PM, Vinod Kone <vinodk...@apache.org> wrote: > Hi, > > As the

Re: 1.1.0 release

I think you need to clean up the JIRA a bit. 1) Make sure unresolved tickets do not have fix version (1.1.0) set. 2) Move "Fix version 1.1.0" to "Target version 1.1.0". 2) might obviate the need for 1). On Fri, Oct 7, 2016 at 7:24 AM, Till Toenshoff wrote: > Hi everyone! >

Re: Threshold-based CPU and Memory Oversubscription

Awesome. Great to see this! Looking forward to the blog post on how this helped utilization in production :P On Wed, Sep 21, 2016 at 10:26 AM, Erb, Stephan wrote: > Hi everyone, > > > > we are happy to announce that we have open sourced two simple > threshold-based

Re: mesos libraries

If you are writing a new scheduler, I would highly recommend using the new HTTP API instead of the Java bindings. This would eliminate the dep on the native library. If you still want to use the old bindings, the easiest way might be to install mesos deb package in your docker image. On Tue, Aug

Re: Mesos 1.1.0 release date

We are planning to release it in a week or so. Till has agreed to be the release manager for the release and will be supported by AlexR. @Till: Can you create a release dashboard and reply to this thread?

Re: Target version vs Fixed Version

that check pick this into > 1.0.x. > > On Tue, Oct 4, 2016 at 9:17 AM, Vinod Kone <vinodk...@apache.org> wrote: > >> Hi, >> >> Going forward, if you want an unresolved issue to be targeted for a >> specific version please set the "Target Version". The

Re: Does libprocess support multi-port?

No it doesn't. On Wed, Oct 26, 2016 at 1:10 AM, Suteng wrote: > Hi, > > Does libprocess support multi port? Some process bind to a port, and some > other process bind to another port in the same OS process. > > > > Thanks, > > Teng > > > > > > > > > > Su Teng 00241668 > > >

[VOTE] Release Apache Mesos 1.0.2 (rc3)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.2. This is a bug fix release. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.2-rc3

Re: On Mesos versioning and deprecation policy

We will chat about this in the upcoming community sync (thursday 3 PM). So, please make sure to attend if you are interested. On Fri, Oct 14, 2016 at 3:44 PM, Yan Xu wrote: > > On Fri, Oct 14, 2016 at 3:37 PM, Yan Xu wrote: > >> Thanks Alex for starting

Re: Force offer from all of the slaves

Once you set GLOG_v, you should be able to see lines like these "Framework filtered agent for <123> seconds" On Sun, Nov 27, 2016 at 8:18 AM, haosdent wrote: > > I choose the right offer and decline the rest. > Hi, @krishnanvr Do you use up all available resources in that

Re: Mesos making offers for no CPU

On Sun, Nov 27, 2016 at 7:53 PM, Christopher Hunt < christopher.h...@lightbend.com> wrote: > My question here though is in the event of receiving a resource offer with > no CPU in it, and then declining it, why shouldn’t my framework receive > offers regarding other nodes with CPU? Surely a

[RESULT][VOTE] Release Apache Mesos 1.0.2 (rc3)

Hi all, The vote for Mesos 1.0.2 (rc3) has passed with the following votes. +1 (Binding) -- Alex Rukletsov Till Toenshoff Yan Xu There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.0.2 It is

[VOTE] Release Apache Mesos 1.0.2 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.2. This is a bug fix release. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.2-rc2

Re: outstanding offers

Are you running a custom framework? Can you see in scheduler logs which offers you are receiving? Am I understanding your question correctly that Mesos thinks offers are being sent to your framework but (you think) your framework hasn't received them? Note that you can increase logging on the

Re: On Mesos versioning and deprecation policy

ected by the > breaking API changes. > > On Sat, Oct 15, 2016 at 6:55 AM, Vinod Kone <vinodk...@apache.org> wrote: > > > We will chat about this in the upcoming community sync (thursday 3 PM). > > So, please make sure to attend if you are interested. > > > > On

Re: Quota

How many resources does the agent register with the master? How many resources does spark task need? I'm guessing marathon is not registered with "test" role so it is only getting un-reserved resources which are not enough for spark task? On Fri, Dec 9, 2016 at 2:54 PM, Vijay Srinivasaraghavan <

Re: Quota

"unreserved_resources":{ > "disk":12099.0, > "mem":14863.0, > "gpus":0.0, > "cpus":4.0, > "ports":"[1025-2180, 2182-3887, 3889-5049, > 5052-8

Welcome Haosdent Huang as Mesos Committer and PMC member!

Hi folks, Please join me in formally welcoming Haosdent Huang as Mesos Committer and PMC member. Haosdent has been an active contributor to the project for more than a year now. He has contributed a number of patches and features to the Mesos code base, most notably the unified cgroups isolator

Re: Mesos YouTube Channel

Thanks for doing this MPark! On Mon, Jan 9, 2017 at 6:21 PM, Michael Park wrote: > I've created a brand channel for Mesos on YouTube for community activities: > https://www.youtube.com/channel/UC0wxLxgX8ilUn0m31lCpzAw. > > The only community activities currently captured in

Re: Authentication module

Authentication is enabled for Mesos APIs used by schedulers (to talk to master), operators (to talk to master/agent) and agents (to talk to master). Executor to agent communication is not currently authenticated. This might throw some light:

Re: Proposal for evaluating Mesos scalability and robustness through stress test.

Great to hear! Haven't looked at the doc yet, but I know some folks from Twitter were also interested this. https://issues.apache.org/jira/browse/MESOS-6768 Probably worth to see if the ideas can be consolidated? On Fri, Jan 6, 2017 at 6:57 PM, Zhitao Li wrote: >

Re: Mesos 1.1.1 release dashboard

Same deal with the next patch release for 1.0.x ;) @vinodkone > On Dec 22, 2016, at 10:15 AM, Alex Rukletsov wrote: > > Folks, > > We are planning to cut the 1.1.1 release early next week. If you have any > patches that need to get into 1.1.1, please make sure that either

Re: Welcome Guangya Liu as Mesos Committer and PMC member!

Congrats Guangya! Welcome to the PMC! On Fri, Dec 16, 2016 at 7:03 PM, Sam wrote: > congratulations Guangya > > Sent from my iPhone > > On 17 Dec 2016, at 3:23 AM, Avinash Sridharan > wrote: > > Congrats Guangya !! > > On Fri, Dec 16, 2016 at 11:20

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

container launch/wait/kill APIs to agent API >> docs. >> >> >> On Wed, Mar 1, 2017 at 11:30 AM, Neil Conway <neil.con...@gmail.com> >> wrote: >> >>> The perf core dump might be addressed if we backport this change: >>> >>> https://r

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

rc2 and back port the perf fix > into 1.1.2. IIUC, time based patch releases should *not be worse*, hence if > the perf issue was already in 1.1.0 it is *fine* to fix it in 1.1.2. I > would like to avoid postponing already belated 1.1.1 for even longer. > > On Wed, Mar 1, 2017 at

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

Tested on ASF CI. Saw 2 configurations fail with https://issues.apache.org/jira/browse/MESOS-7160 I think @jpeach and @bbannier were looking into this. Not sure about the severity of the issue, so withholding my vote. *Revision*: b9d8202a7444d0d1e49476bfc9817eb4583beaff -

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

Tested on ASF CI. Saw 2 configurations fail. One was the perf core dump issue . Other is a known (since 0..28.0) flaky test with Docker fetcher plugin . Withholding the vote until we know the

Re: resourceOffer

> Sure, there they are. > > > On Tuesday, March 7, 2017 12:34 PM, Vinod Kone <vinodk...@gmail.com> > wrote: > > > Can you share master log? > > @vinodkone > > On Mar 7, 2017, at 2:54 AM, Oeg Bizz <oegb...@yahoo.com> wrote: > > Hi, >I am new at

[VOTE] Release Apache Mesos 1.0.4 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.4. 1.0.4 includes the following: * [MESOS-2537] - AC_ARG_ENABLED checks are broken * [MESOS-6606] - Reject optimized builds

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

buntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> On Mon, Apr 17, 2017 at 4:49 PM, Adam Bordelon <a...@mesosphere.io> wrote: > -0, wish we could include the fix for https://issues.apache.org/jira &

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

+1 (binding) Tested on ASF CI. The 2 red builds are known flaky tests (health checks) and a perf core dump issue that's fixed on HEAD. *Revision*: 1beaede8c13f0832d4921121da34f924deec8950 - refs/tags/1.3.1-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl

Re: How to detemine Mesos Capabilities?

When a scheduler registers or re-registers with the master, `MasterInfo` is provided as the callback. This includes the version information which can be used to determine which capabilities a Master has. This is admittedly not great; there is a ticket to introduce Master capabilities and include

Fwd: Github's disappearing mirrors

FYI -- Forwarded message -- From: Chris Lambertus Date: Fri, Apr 28, 2017 at 12:22 PM Subject: Github's disappearing mirrors To: committers Hello committers, We have received quite a few reports of github mirrors gone missing. We’ve

Re: dynamic resource reservations

Typically a framework with no role cannot use resources reserved for another role. So, it would be interesting to see what happened. Also, please be aware that directly upgrading from 0.28.0 to 1.3.0 is not supported. You need to go from 0.28.0 to 1.0.0 and then jump from 1.0.0 to 1.3.0. On Fri,

Re: Containerizers & Executors

See my answers inline. > 1. Mesos Containerizer > - posix isolators > - cgroups isolators > Mesos container also allows you to use custom isolators. > 2. Docker containerizer > - docker isolators > Docker containerizer doesn't have a concept of isolator(s).

[VOTE] Release Apache Mesos 1.0.4 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.4. 1.0.4 includes the following: * [MESOS-2537] - AC_ARG_ENABLED checks are broken * [MESOS-6606] - Reject optimized builds

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

%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> [image: Success] <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/32/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,la

<    1   2   3   4   5   6   >