Re: --resources documentation

Hi John, You are correct, memory & disk are specified in MB. This is documented at http://mesos.apache.org/documentation/attributes-resources/ in the section titled "Predefined Uses & Conventions". Cheers, Greg On Tue, Aug 4, 2015 at 6:54 AM, John Omernik wrote: > Hey, all, I am looking to set

Re: mesos 0.24 released?

Hi Craig, 0.24.0 has been released, the vote that selected 0.24.0-rc2 as the final release passed on Sept. 4, which matches the date from that tarball. Cheers, Greg On Fri, Sep 18, 2015 at 10:57 AM, craig w wrote: > So RC releases are still going out, it's not yet "final"? > On Sep 18, 2015 12:

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

Successfully built `sudo make distcheck` on CentOS 7.1 and Ubuntu 14.04 with only expected test failures. On our Fedora 22 CI build, however, while the tests are building the following compile-time error is produced: [17:18:46][Step 4/6] CXX tests/containerizer/mesos_tests-composing_containeriz

Re: Executor can't start d-bus communication

Hi Pradeep, Can you tell us a bit about your executor: in particular, did you write it against the Executor API , or is it a plain executable that gets run through the command executor? Cheers, Greg On Wed, Oct 14, 201

Re: Executor can't start d-bus communication

nents as user, its worked. > > I wrote the executor using the Executor APIs. By creating a new class. > > Thanks for your reply. > > Regards, > Pradeep > > > On 14 October 2015 at 17:18, Greg Mann wrote: > >> Hi Pradeep, >> Can you tell us a bit abou

Re: mesos fetch uri when behind a squid proxy

It's possible that Spark sets the executor environment explicitly, which would lead to the http_proxy and https_proxy environment variables not being passed along to the executor. You could try using the `--executor_environment_variables` command-line flag when running the agent to specify these en

Re: Welcome Kapil as Mesos committer and PMC member!

Woo!!! Congrats, Kapil :-D On Thu, Nov 5, 2015 at 8:09 AM, Jojy Varghese wrote: > Congratulations Kapil. > > On Nov 5, 2015, at 7:29 AM, Marco Massenzio wrote: > > Awesome stuff! > Congratulations, Kapil - totally deserved! > > On Thursday, November 5, 2015, Vinod Kone wrote: > >> welc

Re: Access to Design Doc

Hi John, I just shared the doc with you; let me know if you still have trouble accessing it. Cheers, Greg On Tue, Jan 12, 2016 at 11:42 AM, John Omernik wrote: > Is there a place to request google doc permissions on the design doc here: > > https://issues.apache.org/jira/browse/MESOS-2840 > > >

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

+1 (non-binding) Note that I discovered a previously-resolved flaky test failure that's cropped back up, noted below. It doesn't seem like a blocker to me, but I wanted to draw attention to it just in case. On a CentOS 7.1 VM, with libevent and SSL enabled: `make check` -> OK `sudo make check` ->

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

+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 On Mon, Feb 29, 2016 at 11:20 AM, Kapil Arya wrote: > +1 (binding) > > Successful

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

+1 (non-binding) `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled. All tests pass except: PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here: https://issues.apache.org/jira/browse/MESOS-4655 CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf, MemoryPr

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

+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 seems to be due to the issue found here: https://issues.apache.org/jira/browse/MESOS-4053 On Mon, Feb 29, 2016 at 2:17 PM, Mi

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

+1 (non-binding) `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled. All tests pass except: PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here: https://issues.apache.org/jira/browse/MESOS-4655 CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf, MemoryPr

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

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://reviews.apache.org/r/44229/ On Tue, Mar 1, 2016 at 9:29 AM, Greg Mann wrote: > +1

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

t; Ubuntu 14.04: `make check` non-root, three failures: > >>> ContainerLoggerTest.DefaultToSandbox [flaky, tracked in MESOS-4615] > >>> MasterQuotaTest.AvailableResourcesAfterRescinding [flaky, tracked in > >>> MESOS-4542] > >>> MasterTest.MaxCompletedT

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

I was also able to successfully test a simple upgrade scenario between 0.25.1-rc1 and 0.26.1-rc1 using Niklas's upgrade testing script, which I've modified slightly and reposted here: https://reviews.apache.org/r/44229/ On Mon, Feb 29, 2016 at 10:31 PM, Greg Mann wrote: > +1

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

+1 (non-binding) `make check` and `sudo make check` on OSX 10.10.5 and CentOS 7.1, with libevent and SSL enabled. All tests pass on CentOS 7.1 When running the sudo tests on OSX, three failures were observed: ExamplesTest.JavaFramework is tracked by https://issues.apache.org/jira/browse/MESOS-35

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

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. All tests pass. I was also able to successfully test a simple upgrade scenario from 0.25.1-rc2 to 0.26.1-rc2 using the script found here: https://reviews.apache.org/r/44229/ Cheers, Greg On Tue, Mar 8,

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

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. The following tests failed during the first test run: ContainerizerTest.ROOT_CGROUPS_BalloonFramework MemoryPressureMesosTest.CGROUPS_ROOT_Statistics MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery bu

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

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. All tests pass. I was also able to successfully test a simple upgrade scenario from 0.23.1 to 0.24.2-rc2 using the script found here: https://reviews.apache.org/r/44229/ Cheers, Greg On Tue, Mar 8, 201

Re: HTTP Basic Auth for Mesos UI

Mi Michal, We have recently enabled authentication on many master/agent endpoints, but authentication doesn't yet work on the webui. Once all the relevant endpoints have authentication enabled, we still need to add a login mechanism to the webui. You can find a ticket for the webui improvement here

Re: Agent won't start

Hi Paul, Noticing the logging output, "Failed to find resources file '/tmp/mesos/meta/resources/resources.info'", I wonder if your trouble may be related to the location of your agent's work_dir. See this ticket: https://issues.apache.org/jira/browse/MESOS-4541 Some users have reported issues resu

Re: Agent won't start

> Paul > > On Tue, Mar 29, 2016 at 5:18 PM, Greg Mann wrote: > >> Hi Paul, >> Noticing the logging output, "Failed to find resources file >> '/tmp/mesos/meta/resources/resources.info'", I wonder if your trouble >> may be related to the loca

Re: Agent won't start

Check out this link for info on /tmp cleanup in Ubuntu: http://askubuntu.com/questions/20783/how-is-the-tmp-directory-cleaned-up And check out this link for information on some of the work_dir's contents on a Mesos agent: http://mesos.apache.org/documentation/latest/sandbox/ The work_dir contains

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

+1 (non-binding) Ran `sudo make check` on CentOS 7 with libevent and SSL enabled; all tests pass. I was also able to successfully simulate a simple upgrade scenario using 'test-upgrade.py'. Note that this initially failed due to some changes made to the test framework in this release, but after a

Re: Disappearing tasks

Hi Justin, I'm sorry that you've been having difficulty with your cluster. Do you have access to master/agent logs around the time that these tasks went missing from the Mesos UI? It would be great to have a look at those if possible. I would still recommend against setting the agent work_dir to '

Re: orphaned_tasks cleanup and prevention method

Hi June, Are these Spark tasks being run in cluster mode or client mode? If it's client mode, then perhaps your local Spark scheduler is tearing itself down before the executors exit, thus leaving them orphaned. I'd love to see master/agent logs during the time that the tasks are becoming orphaned

Re: how to change mesos resources

Hi Stefano, The agent saves its resource information on the disk, so that it can recover in case of failure. When the agent starts up, it checks the work directory, and if it finds information left behind by a previous instance of the agent, it loads that information and attempts to register with t

Re: orphaned_tasks cleanup and prevention method

gt; > Thanks, > June Taylor > System Administrator, Minnesota Population Center > University of Minnesota > > On Thu, Apr 7, 2016 at 3:37 PM, Greg Mann wrote: > >> Hi June, >> Are these Spark tasks being run in cluster mode or client mode? If it's >>

Re: mesos/kafka issues (org.apache.mesos.Scheduler)

Hi Justin, Do you have master/agent logs from a time when these tasks would have gone missing from the Mesos UI? What location are you using for the work_dir on the agents? Cheers, Greg On Mon, Apr 11, 2016 at 1:41 PM, Justin Ryan wrote: > Update : I noticed one of the clusters had a framewor

Mesos Community Sync 4/7/16 - Notes

Hey Mesos community, Find below the notes from our last Mesos Community Sync meeting, which occurred on 4/7/2016 at 9am PST. The next community sync will be on 4/21/2016 from 3-4pm PST. See the Mesos community calendar for upcoming meetings (note that you can a

[Proposal] Remove the default value for agent work_dir

Hey folks! A number of situations have arisen in which the default value of the Mesos agent `--work_dir` flag (/tmp/mesos) has caused problems on systems in which the automatic cleanup of '/tmp' deletes agent metadata. To resolve this, we would like to eliminate the default value of the agent `--wo

Re: [Proposal] Remove the default value for agent work_dir

value for agent work_dir > > how about /opt/mesos/ > +1 > > 2016-04-13 12:44 GMT+08:00 Avinash Sridharan : > >> +1 >> >> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu wrote: >> >>> +1 >>> >>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach

Mesos Community Sync Notes

Hello all! Today we had another Mesos community sync meeting; find the notes pasted below. Of particular interest is our new roadmap document , which outlines items planned for development within the next six months. For future

Community Sync Notes

Hello all! We had some great discussion yesterday during the Mesos community sync, you can find the notes below. Cheers, Greg Mesos Developer Community Sync http://mesos.apache.org/community/ May 19, 2016 Time: 3pm PST Location: Mesosphere HQ Attendees: Mesosphere: Greg M., Gilbert, Artem,

Persistent Volume API Change

Hello all, I'm currently working on MESOS-5005 , which is fixing a small bug in the persistent volumes API. When a new persistent volume is created, a `DiskInfo` message is included in the disk resources of the volume. Nested within another message

Re: Understanding offers

Hi Nihal, Mesos makes decisions about resource allocation for frameworks based on the Dominant Resource Fairness (DRF) algorithm [1]. There are a couple different ways to affect the offers provided to a particular framework: you can assign a *quota* to the framework's role to give it a guarantee th

Re: Welcome Anand and Joseph as new committers!

Congrats guys!!! Very well-deserved! :-D On Thu, Jun 9, 2016 at 2:00 PM, Vinod Kone wrote: > Hi folks, > > I'm happy to announce that the PMC has voted in *Anand Mazumdar *and *Joseph > Wu* as committers and members of PMC for the Apache Mesos project. > > A little about the new committers. > >

Re: Accepting resources with role as framework

Wil, Yes, the framework needs to include the role. Note that if a framework doesn't specify the resource's role, the field will be populated with the default value `*` automatically by the protobuf library when the message is serialized. So, any resource object accepted by your framework will actua

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

+1 (non-binding) * Ran `sudo make distcheck` successfully on CentOS 7.1 with only one test failure: ExamplesTest.PythonFramework fails for me the first time it's executed as part of the whole test suite, and then succeeds on subsequent executions. I'm investigating further, and will file a ticket

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

+1 (non-binding): * Ran "sudo make distcheck" on CentOS 7 with libevent and SSL enabled. All tests passed. * Used "test-upgrade.py" to test upgrades from 0.28.2 -> 1.0.1 and 1.0.0 -> 1.0.1; both were successful. Cheers, Greg On Wed, Aug 10, 2016 at 5:32 PM, Vinod Kone wrote: > Hi all, > > > P

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

Whoops! Sorry y'all, my wires got crossed :) I ran these tests on Ubuntu 14.04. G On Fri, Aug 12, 2016 at 12:50 PM, Greg Mann wrote: > +1 (non-binding): > > * Ran "sudo make distcheck" on CentOS 7 with libevent and SSL enabled. All > tests passed. > * Used &quo

Re: Resource Isolation in Mesos

Hi Srikant, Without using cgroups, it won't be possible to enforce isolation of cpu/memory on a Linux agent. Could you elaborate a bit on why you aren't able to use cgroups currently? Have you tested the existing Mesos cgroup isolators in your system? Cheers, Greg On Tue, Sep 6, 2016 at 9:24 PM,

Re: missing documentation: view_frameworks, view_tasks etc in mesos 1.0

Hi Haripriya, I just ran a quick test using your ACLs (I added a permissive ACL for "run_tasks" as well), and I was able to view everything in the web UI. I did this test with the current HEAD of Mesos master, however, so it's possible that something has changed since 1.0. One thing that can be ve

Re: missing documentation: view_frameworks, view_tasks etc in mesos 1.0

at comes with open source mesos > 1.0. > To configure view_tasks, view_executors, access_sandboxes, do we need > additional authentication added to the exisiting mesos UI? > > From the UI how does it recognize User A to be User A? Are there any > assumptions that I'm missing? What

Re: mesos marathon roles

Hi Vincent, Can you confirm it's because I didn't set any static reservation ? > Yes, that's correct. So how could I check the resource allocation with multiple marathon > instances and roles, and configured weights between these roles ? Is > Marathon supposed to reserve resources with the role

Re: mesos marathon roles

different roles ? I thought I could let everything unreserved (role > *) and the DRF would use the weights to assign those unreserved resources > to roles "foo" and "bar" ? > > 2016-09-08 6:19 GMT+02:00 Greg Mann : > >> Hi Vincent, >> >> Can you

Re: Mesos 1.0.1-2.0.93.centos65 error on rpm installation.

Hi Sarjeet, Sorry for the delayed reply! I was just able to install Mesos 1.0.1 successfully on CentOS 6.6 by doing the following: sudo rpm -Uvh http://repos.mesosphere.com/el/6/noarch/RPMS/mesosphere-el-repo-6-0.noarch.rpm sudo yum install mesos Note that this ends up installing a slight

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

+1 (non-binding) Did `sudo make check` on CentOS 7. Aside from several LinuxFilesystemIsolatorTests and two other flaky tests, CgroupsAnyHierarchyWithFreezerTest.ROOT_CGROUPS_DestroyTracedProcess and MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery, everything passed. Cheers, Greg On Wed, Nov

Re: Welcome Haosdent Huang as Mesos Committer and PMC member!

Congratulations Haosdent!!! :D On Fri, Dec 16, 2016 at 11:08 AM, Zhitao Li wrote: > Congrats Haosdent! Well deserved! > > So glad and honored to work with you! Very impressed with your amount of > contribution on many tasks. > > > > On Fri, Dec 16, 2016 at 10:59 AM, Vinod Kone wrote: > >> Hi fo

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

Congratulations Guangya!!! :D On Fri, Dec 16, 2016 at 11:10 AM, Jie Yu wrote: > Hi folks, > > Please join me in formally welcoming Guangya Liu as Mesos Committer and PMC > member. > > Guangya has worked on the project for more than a year now and has been a > very active contributor to the proje

[Design Doc] [RFC] Executor Authentication

Hello all, As part of the continuing effort to secure all communication in a Mesos cluster, we would like to add authentication to the executor HTTP API. Linked below is a design document draft for this feature; I would love to get the community's feedback! Feel free to leave comments on the Google

Re: [Design Doc] [RFC] Executor Authentication

ec 23, 2016 at 7:00 PM, Greg Mann wrote: > Hello all, > As part of the continuing effort to secure all communication in a Mesos > cluster, we would like to add authentication to the executor HTTP API. > Linked below is a design document draft for this feature; I would love to >

Re: [MESOS-6240] Allow executor/agent communication over non-TCP/IP stream socket.

Hi Bingqiang, I've had some recent discussions with folks about this feature; it's something we are interested in doing but I'm not sure what its priority is in relation to other tickets. While the AF_UNIX address type has been added to libprocess, libprocess does not currently accept domain socke

Re: Question on dynamic reservations

Hi Povilas, Another approach you could try is to use dynamic reservations only. You could either: 1. Alter your stateful framework to dynamically reserve the resources that it needs, or 2. Add a script to your cluster tooling that would make use of the operator endpoint for dynamic res

Re: Question on dynamic reservations

rticularly disk resources) > with attributes on them you could have frameworks voluntarily choose not to > consume resources not meant for them. > > e.g. Disk resource has attribute `CASSANDRA`. Ok, since I'm a Kafka > framework I won't go use that disk. > > On Tue, Jan 1

Re: Welcome Neil Conway as Mesos Committer and PMC member!

Congratulations Neil!!! :D On Sun, Jan 22, 2017 at 4:46 PM, Neil Conway wrote: > Thanks for the kind words, everyone! It's been a pleasure to be a part > of the Mesos community, and I'm looking forward to continuing to > contribute. > > Neil > > On Sun, Jan 22, 2017 at 2:16 PM, Benjamin Mahler

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

I wanted to give a heads up on a flaky test failure I've encountered while testing this RC: 'DockerRuntimeIsolatorTest.ROO T_INTERNET_CURL_DockerDefaultEntryptRegistryPuller'. One issue related to this test was resolved recently (https://issues.apache.org/ jira/browse/MESOS-6001), but this seems to

Re: Welcome Kevin Klues as a Mesos Committer and PMC member!

Woowoo! Congrats Kevin!! On Wed, Mar 1, 2017 at 2:26 PM, Avinash Sridharan wrote: > Awesome !! Congrats Kevin !! > > On Wed, Mar 1, 2017 at 2:07 PM, Jie Yu wrote: > >> Congrats! Kevin! Well deserved! >> >> On Wed, Mar 1, 2017 at 2:05 PM, Benjamin Mahler >> wrote: >> >> > Hi all, >> > >> > Plea

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

+1 (non-binding) Ran `sudo make check` on CentOS 7 with Docker 1.12.1. The only test failure was: ProvisionerDockerPullerTest.ROOT_INTERNET_CURL_Whiteout While I haven't had a chance to look deeply into this, it seems that the whiteout handling was not correct at the time of 1.0, and these changes

Re: Welcome Gilbert Song as a new committer and PMC member!

Congratulations Gilbert!! :D On Wed, May 24, 2017 at 12:01 PM, Avinash Sridharan wrote: > Congrats Gilbert !! Very well deserved !! > > On Wed, May 24, 2017 at 11:56 AM, Timothy Chen wrote: > > > Congrats! Rocking the containerizer world! > > > > Tim > > > > On Wed, May 24, 2017 at 11:23 AM, Zh

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

017 at 2:42 PM Vinod Kone wrote: > > > Hi folks, > > > > Please welcome Greg Mann as the newest committer and PMC member of the > > Apache Mesos project. > > > > Greg has been an active contributor to the Mesos project for close to 2 > > years n

[Design Doc] An Improved KillPolicy

Hello all! I've been working on a little design for some improvements to the KillPolicy. You can find the design doc here . TL;DR: the plan is to extend the KillPolicy message to allow the initiation

This Month in Mesos - December 2017

Dear Apache Mesos Community, Development in Mesos has been active lately, with work taking place to enable things like hybrid cloud and network storage support, as well as improvements to the scheduler API designed to make the lives of framework developers easier. Apache Mesos version 1.5 is just

This Month in Mesos - January 2018

Dear Apache Mesos Community, Happy new year! Here's your latest update on happenings in Mesosworld over the past month. *Working Groups* The working groups have been active; here's a brief summary of recent developments, along with links to the agenda documents. If you see anything that interes

This Month in Mesos - February 2018

Dear Apache Mesos Community, Hello all! I've got a short update for you this month with recent happenings in Mesosland: *Working Groups* Here's the latest from the working groups. Working group meetings can be found on the Mesos community calendar

API Working Group - First Meeting Tomorrow

Hello all, We'll be having our first API working group meeting tomorrow, March 6 at 11am PST. This working group is a great opportunity for us to work toward greater consistency and usability of our API, as well as raise issues with the current interface and plan future directions. You can find th

Release policy and 1.6 release schedule

Hi folks, During the recent API working group meeting [1], we discussed the release schedule. This has been a recurring topic of discussion in the developer sync meetings, and while our official policy still specifies time-based releases at a bi-monthly cadence, in practice we tend to gate our rele

Re: Mesos master endless attemps to kill unexisting task

Hi Adam, The KILL calls are being sent to Mesos by Marathon. Since the KILL call is being forwarded to the agent, it seems that the Mesos master is aware of the task. Could you verify that the tasks show up as running in the Mesos UI? You say that the tasks don't exist anymore - how did you verify

API Working Group Meeting Today

Hey folks, Sorry for the late reminder - the API working group will meet this morning at 11am PST. Zhitao will be presenting the new volume resizing feature he's designing, and we'll have a discussion on the current state and future directions of the Mesos CLI. If you have any other items for discu

Re: Release policy and 1.6 release schedule

it takes from first RC being cut to >> the final release tag vote passes. That probably indicates smoothness of >> the release process and how good the quality control measures. >> >> I would argue for not delaying release for new features and align with the >> schedule

Re: Release policy and 1.6 release schedule

> > I think the burden of maintaining a release branch is not just > backporting. We need to run CI to make sure every maintained release branch > are working, and do testing for that. It's a burden if there are too many > release branches. > > That's a good point, we do need to run CI on all supp

Re: Release policy and 1.6 release schedule

gt; > > I also agree with folks that there're benefits doing releases more > > frequently. Given the historical data, I'd suggest we do quarterly > > releases, and maintain three release branches. > > > > - Jie > > > > On Fri, Mar 23, 2018 at

This Month in Mesos - March 2018

Oh hai there Apache Mesos Community! Back again with your monthly update on current events in the Mesosverse: *Working Groups* Below you'll find a brief summary of the group meetings from this past month, as well as some info about related work that's been happening in the project. Working grou

[API WG] Meeting today

Hi all, The API working group will be meeting today at 11am PST. We'll be discussing HTTP return codes in Mesos [1]. If you have any other items for discussion, add them to the agenda! [2] Cheers, Greg [1] https://issues.apache.org/jira/browse/MESOS-7697 [2] https://docs.google.com/document/d/1J

Re: Mesos master endless attemps to kill unexisting task

irm No kill ack received for instance >> [pub_api_oecd-rest-api-on-port-20015.marathon-196f414a-f61f-11e7-856c-f6e84742f1ef], >> retrying (73402 attempts so far)i cannot find this UUID in Mesos interface. >> >> Regards, Adam. >> >> On 03/15/2018 05:47 PM, Greg Mann wr

Re: Release policy and 1.6 release schedule

Hey folks, I've posted a proposed update to our documented release schedule: https://reviews.apache.org/r/66454/ Please take a look and comment! Cheers, Greg On Mon, Mar 26, 2018 at 11:34 AM, Greg Mann wrote: > +1 for quarterly. I would also say that we should support 3 releases

Re: Release policy and 1.6 release schedule

Thanks for the reviews, y'all! I've got a few "Ship-Its" - I'll commit this later today unless I hear any objections. Cheers, Greg On Wed, Apr 4, 2018 at 11:49 AM, Greg Mann wrote: > Hey folks, > I've posted a proposed update to our documented release sche

Proposal: Constrained upgrades from Mesos 1.6

Hi all, We are currently working on patches to implement the new GROW_VOLUME and SHRINK_VOLUME operations [1]. In order to make it into Mesos 1.6, we're pursuing a workaround which affects the way these operations are accounted for in the Mesos master. These operations will be marked as *experiment

Re: Doc-a-thon May 24th?

Sounds good to me - thanks Judith!! On Wed, Apr 11, 2018 at 1:35 PM, Judith Malnick wrote: > Hi All, > > I'd like the next Mesos Doc-a-thon to happen on May 24th from 3-8pm > Pacific time. I picked the date because it's best for Ben H. > > Does anyone have major reasons why this wouldn't work? I

[API WG] Meeting tomorrow

Hey folks, The API working group will be meeting tomorrow at 11am PST. We'll be chatting about CPU guarantees and limits. Feel free to add items to the agenda ! Cheers, Greg

UPDATE: Mesos 1.6.0 release

Hi all, Several contributors who are either assignees or shepherds for 1.6 blocker tickets (myself included) have recently been pulled into some high priority internal work, so unfortunately I would like to delay the cut of the first release candidate for Mesos 1.6.0 to ensure that we have adequate

[API WG] Meeting tomorrow!

Hi all, The API working group will meet tomorrow, May 1, from 11:00-11:50am PST. We'll be chatting about a proposal for per-framework metrics . Feel free to add more items to the agenda doc

UPDATE: Mesos 1.6.0 release

ppreciated. I have created the 1.6.x branch and *will cut Mesos 1.6 RC1 on Monday, May 7. *Keep your eyes peeled on the mailing list for the email, your help in testing is greatly appreciated! Thanks for your patience! Cheers, Greg On Tue, Apr 24, 2018 at 3:44 PM, Greg Mann wrote: > Hi a

[VOTE] Release Apache Mesos 1.6.0 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.6.0. 1.6.0 includes the following: * Resizing of persistent volumes for agent default resources * Offer operation feedback for resource prov

Re: Getting roles' info in Scheduler

Hi Pascal, This isn't possible directly with the SchedulerDriver, but your scheduler could use the 'GET_ROLES' call of the operator API [1] for this purpose. Cheers, Greg [1] http://mesos.apache.org/documentation/latest/operator-http-api/#get_roles On Sat, May 5, 2018 at 3:37 AM, Pascal Gillet

[RESULT][VOTE] Release Apache Mesos 1.6.0 (rc1)

Hi all, The vote for Mesos 1.6.0 (rc1) has passed with the following votes. +1 (Binding) -- Vinod Kone Chun-Hung Hsiao James Peach Zhitao Li Andrew Schwartzmeyer There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/meso

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

+1 (binding) I did `sudo make check` and verified that only expected flaky tests failed. Cheers, Greg On Fri, May 11, 2018 at 12:35 PM, Gilbert Song wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.5.1. > > 1.5.1 includes the following: > ---

Soliciting documentation feedback

Hi everyone, As part of our ongoing effort to improve the Mesos docs, we're looking for your help. What areas of the Mesos documentation need the most improvement? Do you have projects to suggest or mistakes to flag? We'll be compiling this feedback into project suggestions for the May 24th Doc-a

Re: Doc-a-thon - May 24th

Hi all, Just a reminder about the Mesos Doc-a-thon coming up next Thursday, May 24 starting at 3pm PST! You can join in person (RSVP here ) or online (link to join ). It would be great to see you there!

Re: Proposing change to the allocatable check in the allocator

Hi all, We had a nice discussion about this in the API working group meeting today. I agree that it's a good idea to do our best to make this change compatible with future updates to the Request call and/or quota. I think it would be beneficial to have a meeting in a few days to brainstorm some ide

[VOTE] Release Apache Mesos 1.6.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.6.1. 1.6.1 includes the following: *Announce major features here* *Announce major bug fixes here* The CHANGELOG for the rel

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

On Wed, Jun 27, 2018 at 11:59 AM Jie Yu wrote: > >> +1 >> >> Passed on our internal CI that has the following matrix. I looked into >> the only failed test, looks to be a flaky test due to a race in the test. >> >> >> >> On Tue, Jun 26, 2018 at 7

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

tical bug that would wipe out persistent data. I'm backporting > this to 1.4, 1.5 and 1.6. > > On Fri, Jun 29, 2018 at 9:05 AM Greg Mann wrote: > > > The failures here are mostly command executor/default executor tests. > > Looking at the test output, it seems that t

Normalization of metric keys

Hi all! I'm currently working on adding a suite of new per-framework metrics to help schedulers better debug unexpected/unwanted behavior (MESOS-8842 ). One issue that has come up during this work is how we should handle strings like the framework n

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

Hey folks, an update on the 1.6.1-rc2 candidate: an issue surfaced after the fix was merged for MESOS-8830, which is being addressed currently. I'll be AFK for the next 3 days, so I'll cut 1.6.1-rc2 this coming Monday. Sorry for the delay! Cheers, Greg On Mon, Jul 2, 2018 at 12:30 PM,

Re: Normalization of metric keys

then this would be complicated by the > presence of slashes in the principal or other user supplied strings. > > On Tue, Jul 3, 2018 at 3:17 PM, Greg Mann wrote: > >> Hi all! >> I'm currently working on adding a suite of new per-framework metrics to >> help schedul

Re: Normalization of metric keys

means I don't know if the user actually supplied > '#%$' or '/'. But using something like percent-encoding would have property > 3. > > On Fri, Jul 6, 2018 at 10:25 AM, Greg Mann wrote: > >> Thanks for the reply Ben! >> >> Yea I suspect the lack

[VOTE] Release Apache Mesos 1.6.1 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.6.1. 1.6.1 includes the following: *Announce major features here* *Announce major bug fixes here* The CHANGELOG for the rel

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

-9002] - GCC 8.1 build failure in os::Fork::Tree. * [MESOS-9024] - Mesos master segfaults with stack overflow under load. * [MESOS-9025] - The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent. Cheers, Greg On Wed, Jul 11, 2018 at 6:15 PM, Greg

  1   2   >