New PMC Chair

Hi community, Just wanted to let you all know that the board passed the resolution to elect a new PMC chair! Hearty congratulations to *Qian Zhang* for becoming the new Apache Mesos PMC chair and VP of the project. Thanks,

Re: [VOTE] Move Apache Mesos to Attic

Peters wrote: > Thanks Vinod. :-) > > > > > Am 09.04.21 um 01:55 schrieb Vinod Kone: > > Hi folks, > > > > Thanks for further responses and strong interest from a few folks in > > keeping the project going! > > > > I also had a chance to

Re: [VOTE] Move Apache Mesos to Attic

Hi folks, Thanks for further responses and strong interest from a few folks in keeping the project going! I also had a chance to talk to some ASF members and it sounds like the ASF preferred option forward in this situation is to keep the project going in ASF. Given all the above, I'm

Re: [VOTE] Move Apache Mesos to Attic

Hi Rich, Thanks for chiming in and providing your perspective. Charles already did a great job summarizing some of the current sentiments in the community above. I wanted to add a couple more points based on my discussions with folks in the community and PMC. Yes, there are some folks who are

[VOTE] Move Apache Mesos to Attic

Hi folks, Based on the recent conversations on our mailing list, it seems to me that the majority consensus among the existing PMC is to move the project to the attic

Re: Next Steps

> > > How many man hours where spend on mesos in 2020, 2019 and 2018? > > Roughly 5-6 ppl (in 2020),10-11 (in 2019), 16-18 (in 2018)

Re: Next Steps

Hi folks, Sorry for the radio silence on my part for the last couple weeks. My Apache emails were not getting delivered to my inbox due to some filter mixup on my end. Sorry about that. I've read through the various threads and here's how I summarize the situation. We basically have 2 camps

Re: Next Steps

Good to see some interest in helping with project maintenance. Qian can you start a new email about figuring out the roadmap for the project? Thanks, Vinod > On Feb 18, 2021, at 11:18 AM, Charles-François Natali > wrote: > > Speaking as someone who contributed a few patches and would like

Next Steps

Hi folks, I would like to start a discussion around the future of the Mesos project. As you are probably aware, the number of active committers and contributors to the project have declined significantly over time. As of today, there's no active development of any features or a public release

Re: Subject: [VOTE] Release Apache Mesos 1.11.0 (rc1)

+1 (binding) We have this version running in an internal cluster without any issues. On Tue, Nov 17, 2020 at 8:53 AM Andrei Sekretenko wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.11.0. > > 1.11.0 includes the following: > >

Re: [AREA1 SUSPICIOUS] [OFFER] Remove ZooKeeper as hard-dependency, support etcd, Consul, OR ZooKeeper

gt;> > >simply alter the interface so that only the version is > returned. > >> >> > >- > >> >> > > > >> >> > >Explicit “session drop” operation that also immediately erases > >> all > >> >&g

Re: Subject: [VOTE] Release Apache Mesos 1.10.0 (rc1)

he workaround for the javah race and the fix for missing dependency on > protoc seem to be rather straightforward. > If any of these two should be considered a blocker for 1.10.0, please vote > -1. > > > > > > On Tue, May 19, 2020 at 6:55 PM Vinod Kone wrote: > >>

Re: Subject: [VOTE] Release Apache Mesos 1.10.0 (rc1)

Ran it in Apache CI. Found 2 build issues (issue 1

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

+1 (binding) Tested on ASF CI. All builds passed! *Revision*: 5f617044c969ebcfca281d043a2474c1a6b39f23 - refs/tags/1.7.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image:

Re: how is the agent available memory computed/updated?

an > analysis and potential fix, it'd be great if someone could have a look > :). > > Cheers, > > Charles > > Le jeu. 30 avr. 2020 à 15:36, Vinod Kone a écrit : > > > > Mesos assumes that it is the only process managing resources of a box > (cpu, > > m

Re: how is the agent available memory computed/updated?

Mesos assumes that it is the only process managing resources of a box (cpu, mem, disk). So if you have out of band processes using up resources it won't be reflected in the resource offers and the box can be overcommitted. There is no runtime periodic check of available resources, it's only

Re: [AREA1 SUSPICIOUS] [OFFER] Remove ZooKeeper as hard-dependency, support etcd, Consul, OR ZooKeeper

Hi Samuel, Thanks for showing interest in contributing to the project. Having optionality between ZooKeeper and Etcd would be great for the project and something that has been brought up a few times before, as you noted. I echo everything that BenM said. As part of the design it would be great

Re: Scheduler driver doesn't detect loss of connection to the master without zookeeper

rk. Unlikely but possible I think. Having the driver detect > and fail upon EOF/socket error would guard against that. > > > > > >> On Thu, 26 Dec 2019, 18:07 Vinod Kone, wrote: >> >> IIRC, the standalone master detector (the detector that's used when using a

Re: Scheduler driver doesn't detect loss of connection to the master without zookeeper

IIRC, the standalone master detector (the detector that's used when using a local ip address of the master and not zk) doesn't re-detect when master process restarts. It's a limitation of that detector since it's mainly used for testing purposes and not recommended for production use. For

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

+1 (binding) Tested on ASF CI. *Revision*: 5e79a584e6ec3e9e2f96e8bf418411df9dafac2e - refs/tags/1.9.0-rc3 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image: Success]

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

ll bundle boost 1.65.0, just like we did during 1.8.x. We > just adjusted our special stripped bundle to include additional headers. > > On Tue, Aug 27, 2019 at 1:39 PM Vinod Kone wrote: > >> -1 >> >> We upgraded the version of the bundled boost very late in the rele

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

-1 We upgraded the version of the bundled boost very late in the release cycle which doesn't give downstream customers (who also depend on boost) enough time to vet any compatibility/perf/other issues. I propose we revert the boost upgrade (and the corresponding code changes depending on the

Re: Restarting mesas-agent kills executors

Need agent and executor logs to diagnose. Can you share them? Thanks, Vinod > On Aug 1, 2019, at 6:05 AM, Jorge Machado wrote: > > Hi Guys, > > I was reading about agent restarts on > http://mesos.apache.org/documentation/latest/agent-recovery/ >

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

+1 (binding). Tested in ASF CI. One build failed due to known flaky test https://issues.apache.org/jira/browse/MESOS-9594 *Revision*: 4ae06448466408d9ec96ede953208057609f0744 - refs/tags/1.8.1-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers

Daily snapshot builds through Jenkins

Hi there, We would like to automate publishing of Mesos snapshot jar to repository.apache.org through a Jenkins job in builds.a.o. Right now we do this manually through a script . I have couple questions that I was hoping you could

Re: '*.json' endpoints removed in 1.7

I propose that we revert this change and keep the ".json" endpoints in master branch and 1.8.x My reasoning is that, we have ecosystem components (e.g., mesos-dns which is yet to have a release with fix) and anecdotally a bunch of custom tooling at user sites that depend on these ".json"

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

+1 (binding) 1 failed build was due to a known flaky test. *Revision*: acefa90695a32f8e8d6361f8192a6522aeaadbb9 - refs/tags/1.8.0-rc3 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools

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

+1 (binding) Ran on ASF CI. *Revision*: f5920ad1a7cbcd2423c30465dcf14948e392081b - refs/tags/1.8.0-rc2 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image: Success]

Re: Subject: [VOTE] Release Apache Mesos 1.8.0 (rc1)

+1 (binding) Ran it on ASF CI. *Revision*: 85462fc183a60ae18d85729bccb1fffb59aa572c - refs/tags/1.8.0-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image: Success]

Re: Mesos on ssl

Hi Jorge. We are hoping to cut 1.8.0 RC within a week. -- Vinod On Fri, Apr 5, 2019 at 12:06 PM Jorge Machado wrote: > Thanks Hsiao, I think it is this, as a build from master works fine for > me. When are we releasing 1.8.0 ? > > > > > On 5 Apr 2019, at 16:52, Chun-Hung Hsiao wrote: > > > >

Re: Apache ReviewBoard not accepting new users

Good news! Looks like the LDAP requirement will be reverted. https://issues.apache.org/jira/browse/INFRA-18071 On Wed, Mar 6, 2019 at 8:16 AM Benno Evers wrote: > Hi everyone, > > I just wanted to share something that caught us off-guard yesterday: it is > currently not possible to register

Re: Bundled glog update from 0.3.3 to 0.4.0

Another thing to keep in mind is that we are very close to release 1.8.0. Is this glog upgrade potentially risky? If yes, maybe we should wait until 1.8 is branched off and then do it on master / 1.9 . On Wed, Mar 27, 2019 at 10:00 AM Benjamin Mahler wrote: > Thanks Andrei! > > Some interesting

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

+1 (binding) Ran in ASF CI. Saw some flaky tests but otherwise looks good. *Revision*: b1dbba03af23b0222d11f2b7ae936d77ef42650d - refs/tags/1.5.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl

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

petitions, but with a different > error. I filed ticket MESOS-9589 > <https://issues.apache.org/jira/browse/MESOS-9589> to track. > > Cheers, > Greg > > On Tue, Feb 19, 2019 at 2:41 PM Vinod Kone wrote: > > > Found a flaky test > > < > > > htt

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

+1 Ran this on ASF CI. The red builds are a flaky infra issue and a known flaky test . *Revision*: 58cc918e9acc2865bb07047d3d2dff156d1708b2 - refs/tags/1.7.2-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers

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

Found a flaky test

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

+1 (binding) Tested on ASF CI. Red builds are known flaky tests or unrelated infra issues. *Revision*: 1fee9b5365bf2424e4768dc1d5209c6c78dfece6 - refs/tags/1.4.3-rc2 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution

Re: need help http api /endpoints

There is no operator API (i.e., http api endpoint in your parlance) to add/kill tasks. Your job master can talk to the framework that launched all your tasks in the first place (marathon?), to add/kill tasks. Most existing mesos frameworks expose add/kill tasks through their own API.

Re: Welcome Benno Evers as committer and PMC member!

Congratulations Benno! On Wed, Jan 30, 2019 at 3:21 PM Alex R wrote: > Folks, > > Please welcome Benno Evers as an Apache committer and PMC member of the > Apache Mesos! > > Benno has been active in the project for more than a year now and has made > significant contributions, including: > *

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

+1 Tested in ASF CI. Red builds are known flakes. *Revision*: fcfe1904e45726ca96fc6707d8b227a16664f4f8 - refs/tags/1.4.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers --disable-parallel-test-execution --enable-libevent --enable-ssl autotools [image:

Re: Shut down modules@mesos mailing list ?

SGTM Thanks, Vinod > On Jan 25, 2019, at 5:31 AM, sebb wrote: > > Does anyone else agree? > Does anyone disagree? > >> On Mon, 21 Jan 2019 at 19:20, Till Toenshoff >> wrote: >> >> Agreed. >> >>> On 20. Jan 2019, at 23:34, sebb wrote: >>> >>> The modules@ mailing list looks as though it

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

+1 (binding) Tested on ASF CI. Failing builds are due to missed SSL dep in the docker build file and a flaky test. *Revision*: d5678c3c5500cec72e22e775d9d048c55c128954 - refs/tags/1.7.1-rc2 Configuration Matrix gcc clang centos:7 --verbose --disable-libtool-wrappers

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

+1 (binding) Passed in ASF CI. Known flaky tests, but otherwise builds look good. *Revision*: 3088295d4156eb58d092ad9b3529b85fd33bd36e - refs/tags/1.5.2-rc3 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Failed]

Re: [Community WG] Reminder: Meeting today at 10:30 AM PST

Cloud recording for those who missed it: https://zoom.us/recording/play/8z2oHhJZIkf0xnJZ40-NtzlNdwn9ev_FuGQnlYkbdp4AFqpHbfWXdO46Us3-MyNu?continueMode=true On Mon, Jan 14, 2019 at 11:49 AM Vinod Kone wrote: > Hi folks, > > This is a reminder that we have community WG meeting today at

[DISCUSS] Updating the support and release policy

Hi folks, As discussed in the Community WG meeting today, I wanted to send out a proposal for updating the current support and release policy . Context: According to our release policy, the latest released version and last 2 released

[Community WG] Reminder: Meeting today at 10:30 AM PST

Hi folks, This is a reminder that we have community WG meeting today at 10:30 AM PST. The agenda for the meeting is here . Please feel free to add more items to the agenda. See you there, Vinod

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

y/CMakeFiles/grpc-1.10.0.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs On Wed, Jan 2, 2019 at 3:35 PM Vinod Kone wrote: > I see an issue > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/57/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbo

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

I see an issue

Re: FW: full Zookeeper authentication

Dmitrii. That approach sounds reasonable. Would you like to work on this? Are you looking for a reviewer/shepherd? On Thu, Dec 6, 2018 at 11:28 AM Kishchukov, Dmitrii (NIH/NLM/NCBI) [C] < dmitrii.kishchu...@nih.gov> wrote: > Mesos allow using only digest authentication scheme for Zookeeper.

Re: New scheduler API proposal: unsuppress and clear_filter

se filtered) offers and hence speed > up the deployment. > > -Meng > > On Mon, Dec 3, 2018 at 12:40 PM Vinod Kone wrote: > > > Hi Meng, > > > > What would be the recommendation for framework authors on when to use > > UNSUPPRESS vs CLEAR_FILTER? > &g

Re: New scheduler API proposal: unsuppress and clear_filter

Hi Meng, What would be the recommendation for framework authors on when to use UNSUPPRESS vs CLEAR_FILTER? Also, should it CLEAR_FILTERS instead of CLEAR_FILTER? On Mon, Dec 3, 2018 at 2:26 PM Meng Zhu wrote: > Hi: > > tl;dr: We are proposing to add two new V1 scheduler APIs: unsuppress and >

Re: Propose to create a Kubernetes framework for Mesos

Cameron and Michal: I would love to understand your motivations and use cases for a k8s Mesos framework in a bit more detail. Looks like you are willing to rewrite your existing app definitions into k8s API spec. At this point, why are you still interested in Mesos as a CAAS backend? Is it because

Re: Welcome Meng Zhu as PMC member and committer!

Congrats Meng! Thanks, Vinod > On Oct 31, 2018, at 4:26 PM, Gilbert Song wrote: > > Well deserved, Meng! > >> On Wed, Oct 31, 2018 at 2:36 PM Benjamin Mahler wrote: >> Please join me in welcoming Meng Zhu as a PMC member and committer! >> >> Meng has been active in the project for almost a

Re: Propose to run debug container as the same user of its parent container by default

Sounds good to me. If I understand correctly, you want to treat this is a bug and backport it to previous release branches? So, you are also asking whether backporting this bug will be considered a breaking change for any existing users? On Thu, Oct 25, 2018 at 11:46 AM James Peach wrote: > >

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

-1 Tested on ASF CI. Looks like Clang builds are failing with a build error. See example build output

Re: Request for Comments - Health Check API Proposal

avoid costly changes/deprecations. On Thu, Oct 18, 2018 at 4:04 AM Alex Rukletsov wrote: > Thanks for the thoughts, Vinod! Answers inlined. > > On Wed, Oct 17, 2018 at 8:55 PM Vinod Kone wrote: > > > One of the things we discussed when we added `CheckInfo` and > > `CheckSta

Re: Mesos Flakiness Statistics

This is great. Thanks Benno for sharing! What did you use to do the analysis? I would love it if we can have graphs that we can run on TVs. On Mon, Oct 15, 2018 at 5:23 AM Benno Evers wrote: > > Is there any reason the first portion of the test name is being > truncated? > > There is, although

Re: Request for Comments - Health Check API Proposal

One of the things we discussed when we added `CheckInfo` and `CheckStatusInfo` was to make the older `HealthCheck` and `bool healthy` field (inside `TaskStatus`) consistent with the new `Check` format. IIRC, some of the changes we wanted to do were - Deprecate `HealthCheck` and introduce a

Re: [dcos] Vote now for MesosCon 2018 proposals!

Voted! I see some really good proposals in there. Really looking forward to the final program! On Thu, Sep 20, 2018 at 11:51 AM Jörg Schad wrote: > Dear Mesos Community, > > Please take a few minutes over the next few days and review what members > of the community have submitted for MesosCon

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

I prefer 1) since you already have the fix. Thanks, Vinod > On Aug 29, 2018, at 8:44 PM, Chun-Hung Hsiao wrote: > > I found two issues when compiling with clang 3.5: > > 1. The `-Wno-inconsistent-missing-override` option added in > https://reviews.apache.org/r/67953/ > is not recognized

Re: MesosCon 2018 Location Change

+1 for Bay area Thanks, Vinod > On Aug 26, 2018, at 12:02 AM, Vaibhav Khanduja > wrote: > > +1 for bay area. > > Thx > >> On Sat, Aug 25, 2018, 3:20 PM Jörg Schad wrote: >> >> Just one more comment on the reasoning here: >> We (i.e., the PC) want MesosCon to be a user-driven conference

Re: This Month in Mesos: August 2018

This is great. Thanks for the update Greg! On Wed, Aug 15, 2018 at 5:29 PM Greg Mann wrote: > Hi all, > My apologies for the lack of emails during the last few months - I'm going > to try to get back into the routine! Here's your August update on recent > developments in the Mesos community,

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

I see some flaky tests in ASF CI, that I don't see already reported. @Kapil Arya Can you take a look at https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/53 and see if the flaky tests are due to bugs in test code and not source? *Revision*:

Re: Build failed in Jenkins: Mesos-Reviewbot #23005

Should be fixed now. On Tue, Aug 7, 2018 at 9:58 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > Started by user vinodkone > [EnvInject] - Loading node

Re: Getting write access to our GitHub repo

Filed: https://issues.apache.org/jira/browse/INFRA-16832 On Mon, Jul 23, 2018 at 6:11 PM Vinod Kone wrote: > Hi Benjamin, > > The main reason for moving to gitbox is to better avail GitHub integration > (i.e., closing stale PRs, directly merge from GH if wanted, lower barrier

Re: Getting write access to our GitHub repo

ople commit to both > >> repos independently and there is slowness in synchronization. > > > > > > +1 on making only github writable. > > > > 3) Our RB server currently points to yet another mirror " > >> git.apache.org/mesos" which has occasi

Re: Build failed in Jenkins: Mesos-Tidybot » -DENABLE_LIBEVENT=OFF -DENABLE_SSL=OFF,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2) #1341

Oh ok. I searched JIRA but couldn't find anything. On Mon, Jul 23, 2018 at 11:19 AM Benjamin Bannier < benjamin.bann...@mesosphere.io> wrote: > > Hmm. Is this new? > > This is about a week old. There’s a fix in progress, > https://reviews.apache.org/r/68001/. > > @jpeach @drexin > > > > On Mon,

Re: Build failed in Jenkins: Mesos-Tidybot » -DENABLE_LIBEVENT=OFF -DENABLE_SSL=OFF,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2) #1341

Hmm. Is this new? On Mon, Jul 23, 2018 at 11:04 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Getting write access to our GitHub repo

ues. Should we move our RB to point to github too? Thanks, On Sun, Jul 15, 2018 at 9:26 PM Jie Yu wrote: > Vinod, can you start a VOTE thread per our discussion during the > committer's meeting. > > On Sun, Jul 15, 2018 at 1:34 AM, Gastón Kleiman > wrote: > > >

[RESULT] [VOTE] Move the project repos to gitbox

Hi, This vote has passed with 7 +1s and no 0s or -1s! +1 (binding) - Vinod Kone James Peach Zhitao Li Andrew Schwartzmeyer Jie Yu Greg Mann Gaston Kleiman I'll file an INFRA ticket to get the process in motion. Thanks, Vinod On Tue, Jul 17, 2018 at 8:27 PM Gastón Kleiman wrote

Re: [Performance WG] Meeting Notes - July 18

Awesome. Thanks for the write up, Ben! On Wed, Jul 18, 2018 at 2:55 PM Benjamin Mahler wrote: > For folks that missed it, here are my own notes. Thanks to alexr and dario > for presenting! > > (1) I discussed a high agent cpu usage issue when hitting the /containers > endpoint: > >

Re: [AREA1 SPOOF] 1.7 release manager?

+dev -- Vinod On Tue, Jul 17, 2018 at 4:20 PM Chun-Hung Hsiao wrote: > I could volunteer unless someone has been waiting for this :) > > On Tue, Jul 17, 2018 at 2:09 PM Greg Mann wrote: > > > Hey folks! > > The question just came up here in the office: who is managing the 1.7.0 > > release?

[VOTE] Move the project repos to gitbox

Hi, As discussed in another thread and in the committers sync, there seem to be heavy interest in moving our project repos ("mesos", "mesos-site") from the "git-wip" git server to the new "gitbox" server to better avail GitHub integrations. Please vote +1, 0, -1 regarding the move to gitbox. The

Re: Backport Policy

>>>> the release manager should ideally be the one who decides on this. > >>>>> > >>>>> I'm a little puzzled by this, why is the release manager involved? As > >>>>> we > >>>>> already document, backports occur when

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

+1 (binding) Ran through ASF CI. Red builds were known health check / check flaky tests. *Revision*: ae82dd5cc6f415916702897acfd3085b6387b118 - refs/tags/1.6.1-rc2 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Failed]

Re: Backport Policy

Ben, thanks for the clarification. I'm in agreement with the points you made. Once we have consensus, would you mind updating the doc? On Wed, Jul 11, 2018 at 5:15 PM Benjamin Mahler wrote: > I realized recently that we aren't all on the same page with backporting. > We currently only document

Re: [Proposal] Replicated log storage compaction

I don't know about the replicated log, but the proposal seems find to me. Jie/BenM, do you guys have an opinion? On Mon, Jul 2, 2018 at 10:57 PM Santhosh Kumar Shanmugham wrote: > +1. Aurora will hugely benefit from this change. > > On Mon, Jul 2, 2018 at 4:49 PM Ilya Pronin > wrote: > > > Hi

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

Hmm. Lot of tests failed when I ran this through ASF CI. Not sure if all of these are known flaky tests?

Re: Getting write access to our GitHub repo

t; >>>>> +1 >>>>> >>>>> Does this means we can add CI webhooks to the git repo? >>>> >>>> FWIW, I'm hugely -1 on doing code reviews on GitHub. I'm cautiously >>>> optimistic about other kinds of integration though. &

Getting write access to our GitHub repo

Hi folks, Looks like ASF now supports giving write access to committers for their GitHub mirrors, which means we can merge PRs directly on GitHub! FWICT, this requires us moving our repo to a new gitbox server by filing an INFRA ticket. We probably need to update our

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

On Wed, May 23, 2018 at 10:00 PM, Michael Park wrote: > > > The tarball has been fixed, please vote now! > > > > 'twas BSD `tar` issues... :( > > > > Thanks, > > > > MPark > > > > On Wed, May 23, 2018 at 11:39 AM, Michael Park wrote: > > &g

Re: Upgrading our support scripts to Python 3

Have we turned python3 on in our CI? Would be great to test. Sent from my phone > On May 24, 2018, at 11:26 PM, Armand Grillet wrote: > > Hi all, > > Python 2.7 will retire on January 1, 2020 and we currently use it for > our support scripts, our Python bindings, and

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

It's empty for me too! On Wed, May 23, 2018 at 11:32 AM, Benjamin Mahler wrote: > Thanks Michael! > > Looks like the tar.gz is empty, is it just me? > > On Tue, May 22, 2018 at 10:09 PM, Michael Park wrote: > >> Hi all, >> >> Please vote on releasing the

Re: [jira] [Commented] (MESOS-8927) Default executor cannot kill tasks if `LAUNCH_NESTED_CONTAINER` is stuck.

Can you paste some logs here too if you have? On Wed, May 16, 2018 at 5:53 PM, Chun-Hung Hsiao (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/MESOS-8927?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel=16478318#comment-16478318 ] > >

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

>>> w/ >>> > CMake on Mac and CentOS 7 with gRPC enabled. >>> > >>> > Observed the following failures: >>> > https://issues.apache.org/jira/browse/MESOS-8884 >>> > https://issues.apache.org/jira/browse/MESOS-8875 >>> > >&g

Re: Deprecating the Python bindings

One of the production users that I know who used to depend on python bindings were https://github.com/douban. Also, apache aurora used to have an executor that depended on python bindings. I don't know what their dependencies are these days w.r.t python bindings. On Wed, May 9, 2018 at 11:51

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

+1 (binding) Ran it on ASF CI. The only failures observed were known flaky command check tests. *Revision*: c7df5eadc075adcf525ea091f65786aaffb9b072 - refs/tags/1.6.0-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Failed]

Re: Add hostname or agentid in rescind offers callback

Can I ask why you are indexing the offers by hostname? Is it to better handle agent removal / unreachable signal? Looking at the code , I think master has the requested information (agent id, hostname) so we can include it

Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

Crashing the agent is definitely not a viable option IMO. Why can't we use agent capabilities instead of agent version and reject such operations at master? This is one of the main reasons we introduced the concept of framework, master, agent capabilities. On Mon, Apr 16, 2018 at 2:04 PM,

Re: This Month in Mesos - March 2018

Thanks for the update Greg! Sent from my phone > On Mar 30, 2018, at 3:08 PM, Greg Mann wrote: > > 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

Re: Adding a `FLAKY` label to flaky unit tests

Would the CI run FLAKY tests or will it filter it out? I'm assuming it still does based on your observation above. What are the other reasons tests are DISABLED today? On Thu, Mar 29, 2018 at 10:35 AM, Meng Zhu wrote: > +1, the advantages are appealing. > > Though I am

Re: 1.6 Release Manager

I would suggest to shoot end of April for the first RC, given our history of first rc rarely being the final rc. Sent from my phone > On Mar 27, 2018, at 10:49 AM, Greg Mann wrote: > > Hey folks, > I'd like to volunteer to manage the 1.6 release. AlexR has kindly offered

Re: Release policy and 1.6 release schedule

I’m +1 for quarterly. Most importantly I want us to adhere to a predictable cadence. Sent from my phone > On Mar 23, 2018, at 9:21 PM, Jie Yu wrote: > > It's a burden for supporting multiple releases. > > 1.2 was released March, 2017 (1 year ago), and I know that some

Re: On disabled tests

Thanks for doing this Alex! Are you proposing a policy that every disabled test should’ve an associated ticket that is linked in the comment above the test? I’m all for it. Sent from my phone > On Mar 21, 2018, at 9:42 AM, Alex Rukletsov wrote: > > Folks, > > to

Re: The state of our CI

Thanks for the reminder MPark. And also huge thanks (to you and others who chipped in) for digging into the blocking fd issue plaguing our CI and fixing it! Please please make sure keeping our CI green is among your top priorities. It's the responsibility of all of us. For new contributors and

Re: Introducing `support/mesos-build.sh`

Yay, thanks MPark! Has the change landed already? On Wed, Feb 7, 2018 at 8:23 PM, Michael Park wrote: > Many of you probably know that we currently have `support/docker-build.sh` > to power our CI for our various configurations. One of the problems for us > has been that we

Re: Soliciting Hackathon Ideas

Versioned documentation! Sent from my iPhone > On Feb 6, 2018, at 4:37 PM, Benjamin Mahler wrote: > > A couple of ideas from the performance related working group: > > -Use protobuf arenas for all non-trivial outbound master messages (easy) > This can be done piecemeal. >

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

+1 (binding) Tested on ASF CI. The red builds were known flaky tests regarding checks/health checks. *Revision*: f7e3872b0359c6095f8eeaefe408cb7dcef5bb83 - refs/tags/1.5.0-rc2 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Failed]

Re: No more Issue update emails

mah...@apache.org> wrote: > This includes any updates to description, priority, target versions? If I > watch a ticket will I still get update emails? > > On Thu, Feb 1, 2018 at 12:29 PM Vinod Kone <vinodk...@apache.org> wrote: > > > Hi folks, > > > > Just a

No more Issue update emails

Hi folks, Just a heads up that I've had our JIRA notification scheme changed so that the issues@ list is no longer emailed when an issue is updated. So no more emails for story point changes or sprint changes! Hopefully you will appreciate the reduction in email to the list. Thanks, Vinod

  1   2   3   4   5   6   7   8   9   10   >